Large processing tables

[Tony Ryder]

I recently had a simlar problem and increased PFLBSIZE to 3000
and have had no troubles since. I did not believe I was anywhere
near the default setting for this variable.

Tony 

-----Original Message-----
From: filepro-list-bounces+tryder=westnet.com.au at lists.celestial.com
[mailto:filepro-list-bounces+tryder=westnet.com.au at lists.celestial.com] On
Behalf Of George
Sent: Friday, February 23, 2007 10:15 PM
To: 'Bruce Easton'; filepro-list at lists.celestial.com
Cc: 'George Simon'
Subject: RE: Large processing tables

From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
[mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
On Behalf Of Bruce Easton
Sent: Thursday, February 22, 2007 1:08 PM
To: filepro-list at lists.celestial.com
Cc: George Simon
Subject: RE: Large processing tables

> George Simon  wrote Thursday, February 22, 2007 12:42 PM : 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.
> For example, a simple code such as:
> If:
> Then: gosub TESTLBL
>
> It will generate an error if TESTLBL is near or at the end of the 
> table but if the label is moved towards the middle or top of the 
> table, the error does not occur.

> I was wondering if anyone out there has a processing table of that 
> size or larger that has experienced the same problem or can test for me.
> Thanks.
> George - do you have the env. var PFLBSIZE set?  And if so, to a high 
> enough value?
 
> Bruce
 
> Bruce Easton
> STN, Inc.

Bruce, as you know, the PFLBSIZE variable has to do with the number of
labels on a table and filePro does give you a warning during syntax check if
it is too small.
I’ve run across that before and my PFLBSIZE is set to 1500.
This error has nothing to do with that since I can move the code up the
table and avoid getting the error.
The problem is that when I move some code up the table, another label gets
to close to the end of the processing table and I start getting a different
error somewhere else.
I'm trying to fix the problem by moving declarations to the bottom of the
table, making some more code part of a "called" table and eliminating some
long-winded comments but this is certainly a PITA and a very serious problem
if you have large enough tables.
The problem seems to manifest itself once a table reaches or exceeds 262,144
bytes.  Peculiar number.

_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list