- Do you have the same version/SP of VFP runtime on the problem machine as was used to build the .EXE?
- Can you try temporarily disabling any antivirus on the problem machine?
- Do you have any code that is reliant on something on your dev machine (environment variable, presence of a file etc.)?
>Perry:
>
>Also, because the program runs fine from VFP I'm not sure if stepping thru will help.
>
>The error message appears in a message box, it's funny that my error routine doesn't catch this an tell me where the problem is.
>
>Like I said, it runs fine on my production machine which is also a WinXP machine (from "RUN" or the actual .EXE), but when loaded on another WinXP machine I have this problem.
>
>Mal
>
>>Public is Public.
>>
>>Somewhere you are releasing the memory variable. You will need to step thru and see where the problem lies.
>>
>>>Hi:
>>>
>>>I'm a little lost and would like a little help.
>>>
>>>The following works find compiled using VFP 7 and loaded on a new Win98 machine.
>>>
>>>I have a logical global variable, "glTable", declared PUBLIC in my main.prg of the project.
>>>When I "run" the program from the project manger, all is well.
>>>When I create an EXE and run it on the same machine, the one with VFP loaded, again, all is well.
>>>
>>>However, when I load the program on a new WinXP machine, my program complains that it can't find variable "glTable".
>>>
>>>I thought global variables were available throughout an entire program once delared PUBLIC.
>>>
>>>Any ideas?
>>>
>>>Mal
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up