Insufficient Memory Error

[CDavis]

I have a small executable that I have loaded on several of our organization's computers. The app is written in VFP 3.0

Today I installed the application on a new computer and immediately received an insufficient memory error. I've looked at the previous posts on this topic and my situation seems to be different. The article that I could find at MS also didn't seem to apply. They indicated that systems with less than 512 MB of RAM running Windows NT were not receiving the error.

The system that I'm having trouble with is using NT 4 with Service Pack 6a and also has Office XP. It has 256 MB RAM.

I'm wondering if anyone else has had a similar problem and a fix.

I could rewrite the app in VFP 6 or 7 but it has been stable and I'd prefer not to spend any more time on it than necessary.

Thanks in advance as usual.

CDavis

 

[rgbean]

KB article

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q148562

- "INFO: List of Problems in Visual FoxPro 3.0 for Windows (Q148562)" also lists using OLE controls may cause this problem.
You say that you receive the error "immediately" - in general what kind of code are you running at the beginning of the program? While you say it has 256KB, what else is running when you fire up this app? How much memory is actually available? Have you tried running the app with "nothing" else running? Has this app ever been run under Win NT (2000/XP) or just under Win 9x?

Rick

 

[CDavis]

Rick,
After I had the trouble earlier I loaded the program on one of our IT director's computer who is using Windows 2000 and had no problem.

I've set the main program to be the menu system and the following is the code I have in the setup of the menu:

ON SHUTDOWN DO MY_SHUTDOWN
ON ERROR DO ERRORHANDLER WITH ERROR(), MESSAGE(), LINENO(), SYS(16)

MODIFY WINDOW SCREEN ICON FILE CDPRO.ICO
MODIFY WINDOW SCREEN TITLE "Cd\Pro Work Request Program"

ON KEY LABEL RIGHTMOUSE KEYBOARD "{ENTER}"

mBldg = "\\appserver1\workorders\depreq\BLDG"
mDepreq = "\\appserver1\workorders\depreq\DEPREQ"

SET CENTURY ON
SET EXCLUSIVE OFF

USE CONFIG IN 0
USE (mBldg) IN 0
USE (mDepreq) IN 0
********************************

The error message must be generated from the support library because it is not reaching the errorhandler that I've set up in my program.

I'm not using any OLE controls so that shouldn't be the problem.

The only other difference is that the computers in question are at remote sites -- but I have the program running on other remote sites with no problems. There are only two small tables being accessed on the server. All the other files are located on the client machine.

Let me know if you think of anything else.
Thanks -- cd.

 

[rgbean]

Just looking at what you've provided, there doesn't seem to be much that can go wrong. I guess the first thing I'd check is the runtime files on the NT system - for matching version and size to a system that is working (just in case a 'virus' got to it). I'd also check to make sure that the machine doesn't have multiple copies somewhere in the path. And while you say it's on 6a, you might want to reapply the Service Pack, in case some later install replaced some critical support file(s).

Rick

 

[rgbean]

I found one more Insufficient Memory reference for VFP 3.0 - "FIX: Insufficient Memory in Visual FoxPro on Fast Computers (Q179287)" at

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q179287.

Unforntunately it's related to comboboxes and it sounds like you are dying before you are firing up any form.

Rick

 

[CDavis]

Rick,
Thanks for the additional suggestions. I've checked the runtime file and its okay. The combobox issue that you pointed me to also doesn't seem to apply. I was at the Seattle Foxpro Special Interest Group last night and the experts I checked with thought that maybe it could be related to an XP issue. I'm going to take it home tonight and try it on my home version of XP to see if I can duplicate the problem there.

Its looking like I may have to upgrade the app to a later version of VFP.

Thanks -- If anyone else wants to chime in, I'd appreciate it.

Chuck