VFP7 program too large?

[SnyAc]

I'm working on updating an older VFP application and I'm getting a 'Program too large' error when trying to compile one of the PRG's in VFP7. What is the program size limitation in VFP7?...

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[Dan Freeman]

It's certainly no smaller than previous versions. Did this program compile previously?

Does the user have *full* rights in the directory containing the code?

 

[SnyAc]

This is a strange one.... the program will compile just fine in VFP9....

the help file for VFP7 gives the following explanation ....

Program is too large (Error 1202)
The program that Visual FoxPro is attempting to load will not fit into memory. The largest program or individual procedure Visual FoxPro can load is one containing 65,000 bytes.




Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[Dan Freeman]

Sounds like a good reason to abandon VFP7. ;-)

 

[SnyAc]

That's the end goal, however I don't have the VFP9 version ready to release yet so I still have to get this compiled in VFP7.

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[SnyAc]

Ok.... FYI ... the error message was referring to individual procedures / functions within the PRG file. this program used do case structures to process instead of calling a procedure for each of the cases.... Problem resolved by creating a procedure for each of the cases and calling the procedure from the case structure....

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[Dan Freeman]

OK, that's just weird.

 

[Olaf Doschke]

Nope, not weird. I also came across this limitation of VFP7 once with a large chain of IFs. An incremental update:

If version<2
   ...
Endif

If version<3
   ...
Endif

If version<4
   ...
Endif

Was for a bigger corporate LAN. I hadn't imagined this to grow that big and fast. But in fact it was helpful to update people coming back from vacation to several versions.

No matter what version a user had this update routine would do all the steps neccessary to update it to the last veriosn. Mainly this was about new config items, new tables or fields etc. (especially a local database, the central database common to all was handled administrative otherwise).

But today I do such things data driven, eg have all the ... code snipet in a memo together with the version it creates and then execute all records with a higher version as the active one.

That aside, because the main point is the 64K limit. As Andy Snyder noticed that's a limitation and as you noticed it's only for procedures and functions, not for whole prgs.

VFP9 has overcome this limitation, I don't know if it existed in VFP8 too, but VFP9 was also the first version to support as large arrays as memory allows.

Bye, Olaf.

 

[SnyAc]

Olaf... this is also an older, corporate LAN driven application.... everything being dragged over the network from the server (exe included).... the VFP9 version will be written properly (executing local, only the data being accessed over the network).

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[baltman]

Look at System Capacities in help under the Program and Procedure Files section.

 

[Dan Freeman]

Sorry, Olaf. It's weird whether you've seen it before or not. ;-)

 

[Olaf Doschke]

LOL, agreed.

 

[dbMark]

As a side note, if you were generating a multithreaded DLL (which you aren't here) and this error 1202 happened occasionally, then VFP allows you to change the setting for PROGCACHE in config.fpw to reserve more memory.