Why?

[George Simon]

No need for all the formalities, I got my answer already...
The filePro theorem:  Ken has not replied to this message, so it must be a
bug. 8-)
But for all you purists out there:
FilePro Version: Native  5.0.09 RN9/DN9
OS: Windows XP Professional
Yes, I tried changing the | with chr("124").  Same result.
Yes, I ran it with dreport instead of rreport.  Same result.
Yes, I ran it with the debugger.  I gives me the error as soon as I hit
<Enter> past the lct= line.  The xlate line does not display, so I guess the
problem is with long dummy variables and *report..
Running the same table from rclerk produces no errors.


George Simon (IT Department)
American River Logistics, LTD
614 Progress St.
Elizabeth, NJ  07205
Phone:(908)354-7746      Fax:(908)354-7491
mailto:george at worldest.com
http://www.americanriverintl.com/



-----Original Message-----
From: GCC Consulting [mailto:gcc at optonline.net]
Sent: Monday, June 28, 2004 7:42 PM
To: 'George Simon'; 'Filepro-List'
Subject: RE: Why?



> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf
> Of George Simon
> Sent: Monday, June 28, 2004 3:13 PM
> To: Filepro-List
> Subject: Why?
>
>
> Does this code:
>
> 14  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
>        ? If:
>        Then: ky="|"
>  15  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
>        ? If:
>        Then: lct=""{gu{ky{gv{ky{gw{ky{gx{ky{gy{ky{ma{ky{mb{ky{me{ky{mf
>  16  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
>        ? If:
>        Then: lct=xlate (lct,"|"," ")
>
> Makes rreport throw up and display this error"
>
>                           Records Selected:        21
>
>                          Generating Output:        21 The
> instruction at
> 0040827
> 7 referenced memory at 00000012?The memory could not be read from
>
> but the same code works just fine in rclerk?
>
> The code is in a "called" table from automatic processing.
George,

Try changing ky=chr(124), which I think is the ASCII code for |.

This might help.

Ken questions:

Have you run the debugger on this code?

What OD and fp version?

Richard Kreiss
GCC Consulting