<< IF(Q.NE.G) GOTO 10>>

What you really need is a line:

IF (USER.NE.REPORT_ACCOUNTING) GOTO DOOR

===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431







Frank Gribbin <[log in to unmask]> on 03/23/2001 10:20:43 AM

Please respond to Frank Gribbin <[log in to unmask]>








 To:      [log in to unmask]

 cc:      (bcc: Leonard Berkowitz/CORP/HPHC)



 Subject: Re: [HP3000-L] Image Data Types








Years ago, we were having an issue with people not reporting the infrequent
Image errors generated by our systems.  So I wrote the following simple
Fortran routine to intercept Basic's XDBEXPLAIN.  It traps the user into
calling us.  As I advocated in a previous thread, this technique is easily
applied to DBPUT & DBUPDATE, using many 3k languages, in order to enforce
your organization's data validation needs, when validation is
appropriate.

$CONTROL SEGMENT=SEGAB
      SUBROUTINE XDBEXPLAIN(S)
      INTEGER S(10)
      CHARACTER*2 Q,B,G
      B[1:1]=%7C
      B[2:1]=%7C
      G[1:1]=%7C
      G[2:1]=%17C
      CALL DBEXPLAIN(S)
10    DISPLAY "Report this to Accounting NOW  !!!  ",B
      ACCEPT Q
      IF(Q.NE.G) GOTO 10
      RETURN
      END

Frank J. Gribbin
Potter Anderson & Corroon LLP


On Fri, 23 Mar 2001 14:52:10 +0100, Lars Appel <[log in to unmask]> wrote:

>PS...
>
>>On the other hand, nobody would have to wait for HP to implement such a
>>feature. As far as I recall, there are already a couple of people/products
>>using an "intercept" approach with Image Intrinsic "look alikes" in some
>>user level NMXL or NMRL that call XL.PUB.SYS internally.
>
>I vaguely recall some nice paper from VeSoft talking about the concept
>and implementation of intercepting intrinsic calls with user XLs or SLs.
>I am not sure, but I think it was at the Adager or Robelle web site.
>
>Lars.