VFP9 - Internal Consistency Error on Win/XP Pro ???

[vfp7guy]

We are VFP developers, and I have recently replaced my local Win/2000 development computer with one using Win/XP-PRO. Installed the same software as on my old computer ... VFP8, VFP9, etc.

Everything seems OK except for the following chronic problem. If I make a syntax error in a line of code while editing a form method, and I try to exit that method, I get the standard VFP warning with the error line highlighted.

But, as soon as I CANCEL, I always get the MS VFP message window "...FoxPro has encountered a problem and needs to close..." with the option buttons to Send Error Report. When I click the "Don't Send" button, I get the "Internal Consistency Error" messagebox and get kicked out of VFP, resulting in all my revisions getting lost. The vfp9err.log shows it as a C0000005 error. Very frustrating!!!

I never had this problem with WinNT/2000, only with this new computer running XP-Pro. Any ideas?

 

[craigber]

Delete the FoxUser.* files in the HOME(7) folder.

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[vfp7guy]

Thanks Craig ... I just tried that now.
I still get the same problem, but with one difference. Now, after I get the above error messages, I get the SAVE CHANGES? option before VFP shuts down.

 

[EzLogic]

Reindex the files.

Ali Koumaiha
Wireless Toyz
Farmington Hills, Michigan

 

[vfp7guy]

Ali, thanks anyway, but I'm not running any program at the time. This problem occurs during MODIFY FORM. It always occurs if I try and close a Method window that I have open for editing and have a syntax error on a line.

I just tried the same thing using VFP8 and it doesn't generate the fatal error ... it properly warns me about the invalid line and allows me to continue anyway.

 

[mkrausnick]

Could it be a directory permissions thing on the XP box? I'm thinking maybe a log file needs to get written or something and the permissions aren't right. Make sure your user login is in the local machine administrators group, if VFP and the code is located on your C: drive.

Mike Krausnick
Dublin, California

 

[craigber]

Check the Wiki...

http://fox.wikis.com/wc.dll?Wiki~C0000005ExError~VFP

http://fox.wikis.com/wc.dll?Wiki~c0000005Error~VFP

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[petebme]

I ran into the "Syntax Error" problem when using MODIFY FORM on a form that I had just copied from VFP 6.0 (where it worked) to VFP 9.0. Turns out that the problem was in a class object that was contained on the form. We had (in VFP 6.0) added a property called TOOLTIPTEXT. If you looked in the Properties memo field for this object, you would see "tooltiptext=". In VFP 9.0, TOOLTIPTEXT is a native property and it regarded the equal sign (all by itself) as the value. This created the "Syntax Error". The solution was to open the class library, edit the object and reset the value of TOOLTIPTEXT to the default value. Having done this, the form opened without error.

I found this by USEing the SCX and deleting all but the most basic records (opening and trailing COMMENT and the basic Class=form record). After deleting, I had to PACK the file - it DOES NOT WORK if you don't pack the table! Having done this, I was able to do a MODI FORM. Then I restored the original SCX, deleted fewer records, PACKed, did a MODI FORM, and so on, until I had isolated the culprit record.

Your problem might not originate in the same place (i.e. user-defined property that is now native to VFP), but the technique might help you find yours.

 

[vfp7guy]

Thanks petebme .... sounds like a good place to start. I'll update this thread if I find anything applicable.