Maximum Number of Declared Variables

[Ian Wood]

________________________________________
From: Kenneth Brody [kenbrody at spamcop.net]
Sent: Wednesday, November 02, 2011 5:56 PM
To: Ian Wood
Cc: filepro-list at lists.celestial.com; Ron Carlino
Subject: Re: Maximum Number of Declared Variables

On 11/2/2011 5:01 PM, Ian Wood wrote:
> I am running into an error when I have more than 71 declared variables in a processing table. I added a new call routine with 3 globally declared variables in my main table and have them declared externally in the called table.
>
> Once the new code is in place, I can go into IUA and update one record, when I go to updated another record, I get a "Memory cannot be read from" error and dclerk.exe stops running (with a lovely windows message telling me so).
>
> If I take the declare out, no problem, if I add any declared variables to another table, I get the same message once I hit 72 declared variables.
> Windows Server 2008
> filePro 5.014
[...]

This is from the 5.0.15 readme:

> (All) #785
>
>     If you have DECLAREd GLOBAL variables in the automatic and/or the
>     input/output table, and then CALL another table which DECLAREs
>     addtional GLOBAL variables, such that the total number of such
>     variables crosses a multiple-of-32 boundary, and then from within
>     the main input/output table execute a non-dash lookup to the main
>     file, filePro may crash.


--
Kenneth Brody

This certainly is a possibility, but not the exact circumstance. I was approaching 64 declared global variables in the main file but didn't hit it, and I had none in the called routine, and there are no declared global variables in the call routing, only declare extern.  I do have non dash lookups to the file that this input table belongs to.  

I did have a non dash lookup to the input table file from the call routine that was new. Seeing as I was already well over the 32 declare globals before this was added, perhaps that is why it suddenly triggered?

I have removed the call routine and do that processing within the input table.  I will dig deeper into this in the morning.

__

IW