VFP 3 and 1G RAM

[normanhk]

Recently I have upgraded my RAM from 512MB to 1G. My VFP 3 then go crazy. When I try to start it, it responds with "Insufficient memory". If I return to 512MB, the program works once again. Altough I also have VFP 8, I need to use VFP 3 occasionally for some old jobs. Is there any possible solution or tweak?
My OS is Windows XP Pro.

 

[Mike Gagnon]

normanhk

This might answer your question.

http://www.tek-tips.com/viewthread.cfm?SQID=875951&SPID=184&newpid=184&page=1

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[dbMark]

Visual FoxPro 6 Service Pack 5 is considered a solid product. Versions prior to that were "works in progress" and had assorted issues. VFP 3.0a could not work with 512MB. VFP 3.0b could not work with 768MB. Either remove memory when running the older program or figure out a way to update the older projects to run in a newer version.

thread184-693717

http://support.microsoft.com/defaul...port/kb/articles/Q137/8/09.ASP&NoWebContent=1

 

[normanhk]

Thank everybody.
It seems that there is no solution. I have to use VFP3 as there are a lot of stuffs written in VFP3. Although I can transfer them to VFP8 easily, but sometimes VFP8 cannot open some forms. Those forms have some errors. VFP3 merely ignore those errors and allow it to run normally. VFP8 does not allow me to use those form at all (even block editing the form to correct the bugs). May be tI shall set up VFP3 in another computer. Physically removing the RAM is too troublesome for me.

 

[Mike Gagnon]

normanhk

I would recommend upgrading, and correct the errors, rather than maintain the "Those forms have some errors. VFP3 merely ignore those errors and allow it to run normally". It does not make for a solid application.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[RickSchummer]

Are these errors being triggered because VFP 8 has a tighter compiler (caught during a build), or are they errors triggered at run-time?

I agree with Mike, your code will be better if you can fix the errors and run it under a more stable version of VFP. You also get the advantages of using a machine with the full compliment of memory.

_RAS

http://www.whitelightcomputing.com

VFP MVP

 

[normanhk]

Thank you for your advices.
Actually I have already upgraded. But there are hundreds of old forms which are very useful to me (actually they are real money). If I don't use VFP3, I can't even go inside and correct the error. It is not feasible to correct all the error as the quantity is so big and the forms are scattered over tens of different projects.
Anyway is there anyway to ask VFP8 to release those error checking? For example, some of my forms have FontSize = 0 and then VFP8 stands still.

 

[RickSchummer]

I understand your problem (having to change numerous source code files in numerous projects). I am working on migrating a project where we run into this problem all the time.

Typically I say just fix it as you need to recompile a project, but sometimes this is not practical. This is not something I typically recommend, but what you could do is capture the Fontsize = 0 error in your ON ERROR routine and ignore it. Then fix the forms on your own timeline.

_RAS

http://www.whitelightcomputing.com

VFP MVP