Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

C00000005 Error and more

Status
Not open for further replies.

fmoore0001

Programmer
Dec 3, 2002
192
US
Guys, I have a new problem with an application that 3000 users are not having a problem with, but one client is. Of course, it is my fault, no theirs.

In the application on this particular machine after a new or repair install, or a reboot, they can run the program just fine, get in print, etc. However, if they exit the program and try to restart they get either a C00000005 error, a instruction error (trying to write to a portion of memory where not allowed) or the program flashes for a second and quits.

As I said, if we reboot, or reinstall the program, we can run again once.

C000000005 I usually associate with a problem printer driver or no printer at all in the system, but their printer drivers are loaded at boot time from the server.

The computer system itself is a Windows 2000 SP2 system. Several other machines in the office, set up the same way, are having a problem at all. Any ideas.

Frank
 
I am not sure what version of VFP you are using, but make sure it is at least 6.0 sp4.

I have seen most of my C000000005 on large views.

Those are just a couple of possibilities.



Jim Osieczonek
Delta Business Group, LLC
 
thread184-419304 suggests it could be a login name issue.

Suggests a possible TAG issue.
SYMPTOMS
When you print a report, you may receive the following error message: Fatal Error: Exception C0000005

CAUSE
This problem can occur if the Tag and Tag2 fields of the report have printer code for a printer that is not currently being used.
RESOLUTION
As a workaround to the problem, delete the contents of the Tag and Tag2 fields. The following code shows....

Suggests that a "dangling reference" might be the issue.

As Jim mentioned, get the latest service pack if you're running 6.

Also potentially helpful:

Brian
 


had the same error but im not sure if deleting foxuser.dbf will work for you.
 
Hi Fmoore0001,
I had "similar" problem 2 month ago.
Try to control the version of SPOOLSS.DLL on the system.

Jean-Paul
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top