memory variable value loss or not accepting assignment

[anyhandle]

I have an application that is working on most machines, with the exception of one machine. I delt with the error messages he was receiving which was nothing more than his machine doesn't seem to hold variable values. He is not running the application over a network. He claims he has enough memory to run it and enough hard drive space to run it. I have files that save the path and asked him to send it to me and it seems his path references are correct.

What would cause his machine to either not accept variable values or only hold the value for a line or two? Is this his operating system since it's not happening to others or is there something I can do or check within my own application as he's not complaining that this is happening with any other applications?

 

[rgbean]

There just isn't enough information here.
1) What version and SP level of VFP are you running?
2) Are you sure he's using the matching runtime files?
3) What OS is he running?
4) How much is "enough" memory?
5) How much is "enough" disk space?
6) When was the last time the system was subjected to a thorough hardware diagnostic? (Since VFP often uses "all" memory it can find, it'll often exercise parts of memory that no other application will!)
7) What's in the CONFIG.FPW file?

Rick

 

[anyhandle]

Thanks for your response:

1) I'm using VFP 7.0 with SP #1. However, there is a possibility his system has not accepted all the new updated dll's as I've just recently changed from 6.0 to 7.0. Two clients have had a problem with MSVCRT40.DLL installing on their system. It will not overwrite their current file. I did wonder if this is the problem, but can't be sure as he didn't get the same message as the other two did.

2) His OS is XP PRO (no testing for this app has been done on an XP machine; however, he has it working successfully with another XP machine)
4) Memory = 383 MB
5) Hard drive = 17 GB Free
6) thorough hardware diagnostic? - He claims he did so because of the problems he's having with this app as it's working on his other machines.
7) Config.fpw = memlimit=90,1024,7168
mvcount=1200
KEYCOMP = WINDOWS

 

[BPeisch]

You should be using MSVCR70.DLL, not MSVCRT40.DLL.

What is the code that's failing? Could it be that the variable is going out of scope?


-BP (Barbara Peisch)

http://www.peisch.com

 

[anyhandle]

RE: You should be using MSVCR70.DLL, not MSVCRT40.DLL. - VFP 7.0 installed both on my machine, so I distributed both.

RE: What is the code that's failing? Could it be that the variable is going out of scope? -- I have the majority of the application kicked off by a class, which causes to see all code sort of within a capsul. Upon start-up of this application, the initial code is not within this capsul. It is these variables were very choosy as to how I assigned variables. For example, within the initial screen, it would not allow me to use thisform.variable=value. Thisform.variable would not take the value. This was true with local scopes prior to the screen. After my last post, the client told me that the application was finally working. It only started working once it reached this 'capsul'. Personally, I don't understand it, but at least it's working.

Thanks for your response.