Large processing tables

George Simon GSimon at americanriverintl.com
Fri Feb 23 07:01:44 PST 2007


I've received a couple of private messages from other that this has
happened to, so at least I know I'm not alone.
Short of upgrading to 5.6 and the obvious solutions like moving some
code to called tables, is there any solution to this problem?

Here is what I have done so far:

I've eliminated some long-winded remarks and moved all declarations to
the bottom of the table, but it is still not enough.

Any other suggestions?

-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at bestweb.net] 
Sent: Friday, February 23, 2007 9:51 AM
To: George Simon
Cc: filepro-list at lists.celestial.com
Subject: Re: Large processing tables

Quoting George Simon (Thu, 22 Feb 2007 12:42:05 -0500):

> I'm having a problem with Native filePro (version 5.0.14 or earlier)
and
> a table that has approximately 4900 lines and a tok size of  262200
> bytes.
>
> It seems that filePro cannot access labels located towards the end of
> the table without generating memory errors or invalid op code errors.
>
> If the offending label is moved towards the top of the table and
> re-tokenize, the error does not occur.
[...]

Pre-5.6, filePro processing was limited to 128K of compiled code.
This was increased to 2MB in the 5.6 release.  It's possible that
you have run into some problem related to this.

(Note that the tok file includes more than just compiled code -- it
also includes all variable definitions, lookup descriptions, string
literals, and so on.  There is no direct correlation between the
size of the tok file and the size of the compiled code.)

--


More information about the Filepro-list mailing list