Why?

[Kenneth Brody]

George Simon wrote:
> 
> 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-)

Alternate theorem:  When you asked this of fpsupport yesterday, I didn't
answer, as I am not fpsupport.

Besides, I can tell you with 99.99% assurance that, if I were to put those
lines in a processing table, I wouldn't have a problem.

However, you haven't told us the field definitions, or contents, of gu, gv,
gw, gx, gy, ma, mb, me, mf, or tcl, so there is no way to answer your
question without more information.

> But for all you purists out there:
> FilePro Version: Native  5.0.09 RN9/DN9

fpsupport will probably tell you to download 5.0.13 and if you still have
problems, make arrangements to send them files.

> OS: Windows XP Professional
> Yes, I tried changing the | with chr("124").  Same result.

I wouldn't expect any change, since the results are identical.

> 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.
[...]
> >        Then: ky="|"
> >        Then: lct=""{gu{ky{gv{ky{gw{ky{gx{ky{gy{ky{ma{ky{mb{ky{me{ky{mf
[...]

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody at spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+