Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Executable Problems...
Message
De
19/05/1999 14:09:36
 
 
À
19/05/1999 11:55:15
Frank Cavone
Monetary Management of Ny, Inc.
Albany, New York, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00220490
Message ID:
00220552
Vues:
27
>to all,
>i have just completed an application, created the .exe and moved it from my test drive and placed it in the 'live directory'. I've run the application from 3 different machines and have had 3 differnt results.
>
>1 - ran it from my machine, (the machine it was created on), it ran ok.
>
>2 - ran it from another machine, it started with no problem and seemed to run ok, but when i exited the program i received the following message -- Microsfot Visual Foxpro - Fatal error: Exception Code = C0000005.
>

This may be DCOM related - see my entry in the FAQ regarding detecting whether DCOM has been installed properly on a system.

>3 - ran it from a 3rd machine and the program did not start at all received the following message -- A required .dll file, mscvrt.dll, was not found.
>

Unless the VFP runtime, including all necessary components, are installed and correctly registered, the VFP created executable will not run. The easiest thing to do is to create a minimal install of the runtime and components (it doesn't have to include your executable) and install the necessary runtime files on each system that will run the VFP app. Simply copying files or making them available in a shared directory is not an adequate installation of the VFP runtime components.

>suggestions please (i will research the problem in the meantime).
>thank you
>frank
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform