Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP 6.0 Produces Error C0000005 on Windows NT 4.0
Message
From
17/03/1999 09:54:26
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Title:
VFP 6.0 Produces Error C0000005 on Windows NT 4.0
Miscellaneous
Thread ID:
00198545
Message ID:
00198545
Views:
56
I recently upgraded to VFP 6.0. I also loaded service pack 2 for Visual Studio.

When I converted an application from VFP 5.0 I received a Fatal Error C0000005 message.

The error occuired in a single application, when I picked the Classes tab of project manager.

Searching Universal Threads archives found many threads concerning this error code, most pointing to DCOM or to RAGE PRO display adapters. All problems seemed to be with Windows 9X operating systems.

We run exclusively on Windows NT 4.0 SP3 (we are still testing SP4). My desktop does have a RAGE PRO display adapter. However, I had the same problem on my Windows NT Compaq Portable which has a generic S3 display. For this reson I discounted the display adapter as the problem.

The problem seemed occur the project manager tryed to display a class library of mine. This could point to DCOM. However MSDN offered no suggestion for downloading DCOM for WIN NT.

I deleted the class library in VFP 5.0 Project Manager and converted the application to VFP 6.0. When I did this the error did not appear.

As further confirmation I added the "bad" class library to another unrelated application in VFP 5.0. When this application was converted to VFP 6.0 it also crashed, displaying the same error.

I then rebuilt the class library (of course it is my BaseApp class, the biggest I have) class by class, method by method and property by property to try to discover what caused the error. I did this by opening the application in both VFP 5.0 and VFP 6.0 and copying from 5.0 to 6.0 through the clipboard.

Of course I completely rebuild the class without getting the error. I now have a completely converted application which can be opened without problems.

However I do not know if I can really trust VFP 6.0. I must continue developing and do not know if there is any way I can continue in VFP 6.0. If I do what is to prevent the problem from re-occurring?

What does MicroSoft say? They claimed they could not reproduce the problem. I have a class library which will cause the problem in Win NT if they are interested.

Can anyone help me gain a warm and fuzzy feeling about VFP 6.0?
Best Regards
Don Simpson
Next
Reply
Map
View

Click here to load this message in the networking platform