Hi Tracy The problem doesn't lie in the number of records being SUMmed but in the number of fields being SUMmed being > 32 Paul
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: 21 November 2019 17:37 To: profoxtech@leafe.com Subject: RE: Fatal error issuing CALCULATE command
Sent by an external sender ------------------------------
Paul, There is no data in the cursor he created. How many records are you SUMming?
Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Paul Newton Sent: Thursday, November 21, 2019 11:29 AM To: profoxtech@leafe.com Subject: RE: Fatal error issuing CALCULATE command
Hi Eric I think that's because the limit is 32 (not 31 as I stated). Try using For x = 1 To 33 and I think you will get the problem. Please let us know Thanks Paul Newton
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Eric Selje Sent: 21 November 2019 16:17 To: profoxtech@leafe.com Subject: Re: Fatal error issuing CALCULATE command
Sent by an external sender ------------------------------
Interesting. I whipped up this test and cannot replicate the problem: CREATE CURSOR crsTest (id i) cCmd = [CALCULATE ] FOR x = 1 TO 32 cField = "Field"+TRANSFORM(x) ALTER table crsTest ADD COLUMN (cField) I cCmd = cCmd + "SUM("+cField+")," NEXT cCmd = cCmd + "AVG(Field1)" &cCmd
On Thu, Nov 21, 2019 at 9:50 AM Paul Newton Paul.Newton@pegasus.co.uk 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.
Has anybody else encountered this issue? Many thanks
Paul Newton
[excessive quoting removed by server]