Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
C0000005 Fatal error when starting VFP6 apps on 1 machin
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00214739
Message ID:
00220190
Vues:
27
Marcus,

Lexmark, Lexus, drive, driver; my brain is going ;-)>>>

If you disabled the numeric processor manually and nothing changed then this problably isn't your problem.

I was also baffled by having an app freeze up in places that had nothing to do with printing. As it turned out, though, there was a dummy report created programatically early on that set the stage for the freeze later on. Once I started putting the =fpreset(), as mentioned in Q183522, after any possible routines that would involve the printer driver the freezing cleared up. Of course the freeze never happened with MS supplied drivers or drivers from other companies.

Ed

>Thanks Ed,
>My wants to be a Lexus driver, I assume you are referring to Lexmark drivers. Seriously, do you think having one of those Printer Status programs running when you try to start a VFP app could cause this? One of my programs has no printer routines or reports, and it failed immediately also. I also disabled the numeric processor, and it still happened. Have you had C00..5 happen with the HP driver issue? I just get blue screens and lock ups. Regardless, I'm certainly going to check on their printers now.
>
>Thanks,
>Marcus.
>
>>Marcus,
>>
>>If your user who is having the problem has a HP printer using the HP Printer Driver that comes from HP and not from MS, there is a problem with HP and Lexus printer drivers and VFP6. See Knowledge Base Q183522. At first glance this may not seem to be related to your problem but try it and see.
>>
>>Ed
>>
>>>I have sent out about 200 copies of my application, and only 1 is having this problem. When they attempt to run the .exe, they immediately get Fatal Error C0000005. I had them try to run another .exe that simply copies files, and does some maintenance, but it gets the same error. They are running Windows98, and I am using VFP6 with all the service packs installed. I even tried loading DCOM98, but it made no difference. I have no _screen commands after the READ EVENTS statement, and in fact the seconds EXE doesn't even have a READ EVENTS. I also issue a ON SHUTDOWN DO myShutdown, and run no SQL statements during the startup program. I know these are common causes of this nasty error. Any Ideas??? Thanks for any feedback.
>>>
>>>Marcus.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform