At 08:17 2019-11-21, Eric Selje <[email protected]> wrote:
[snip]
Sorry for hijacking your post, Eric, but the original post did
not make it to me.
On Thu, Nov 21, 2019 at 9:50 AM Paul Newton <[email protected]>
wrote:
> Hi all
>
> I think I have come across a possibly undocumented limitation to the
> maximum number of expressions in a CALCULATE command. In my case a fatal
> error occurred when trying to CALCULATE the SUMs of 32 different fields in
> a cursor. It took a while to establish what was going on, but when I
> reduced the number of expressions to 31 the error no longer occurred.
Which fatal error? There are many, and error messages are helpful.
> Has anybody else encountered this issue? Many thanks
How long is the source line? The limit is 8192. Are you
running into that?
Experimenting with long lines, the error I get is either
Line is too long.
if there is no .fxp and
<filename.fxp> is not an object file.
if there is one. Either way, there is no .err file generated even if
I explicitly compile with the compile command.
My client billing app has a source line that is close to 6K
long in actual command, but it has line continuations and &&
comments. I have not experimented, but one of the two prevents the
line from being too long as otherwise the source line would be just
over 20K long.
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
