Visual FoxPro Fatal Exception Error C0005

[FoxDave]

Has anyone experienced the above error when using the following code constructions

THISFORM.methodname(
THISFORMSET.methodname(

I have been using these code constructions when attempting to set up code within a form or formset that will allow the passing of parameters to a method of the form or formset. The error occurs when typing the opening parenthesis. At first I thought that it was peculiar to one PC running Windows NT4.0 but it has also now occurred on a Windows 2000 PC. I have avoided the error by using global variables instead of passing parameters but it would be good to know if there is a solution out there.
I may be wrong but the error appears to suggest that FoxPro is trying to address a piece of memory that is either corrupt, invalid or locked by another application.

 

[Mike Gagnon]

FoxDave

What version of VFP, I thought that one got fixed with a Service pack. Mike Gagnon

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

 

[FoxDave]

FoxPro version 7.0

I have tried installing Service Pack 1 but this had no effect on the NT machine. I am not aware of any later service packs.
There was a similar error fixed in service pack 1 which occurred with CREATEOBJECT() when you programmtically call Microsoft Visual SourceSafe. I am not using SourceSafe yet.

 

[Mike Gagnon]

FoxDave

If you are a registered user of VFP you have access to their help desk? I do not develop on NT4, but I did encounter the problem you mention on Win98, but either an uninstall and re-install or the addition of the SP1 corrected the situation. This may worth a call to Microsoft as changing your programming techniques might be suitable workaround but there must be a better fix. Mike Gagnon

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

 

[IRABYY]

FoxDave (IS/IT--Manageme)
FoxPro version 7.0

I have tried installing Service Pack 1 but this had no effect on the NT machine. I am not aware of any later service packs.

Dave,

Installing the latest SP for WinNT itself also may help. My "partner in crime" - co-worker - also experienced problem similar to yours on NT4, but SP - don't remember which one exactly, 3 or later - helped.

I believe there are also SP3 for NT5/2K out there.

Try it, it may help.

Regards,

Ilya