Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Problem with startup of .EXE
Message
De
09/01/2000 08:14:49
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00315104
Message ID:
00315107
Vues:
17
>I have an SP3 VFP6 application (.EXE) in a directory with three VFP6R files, my foxuser files and a CONFIG.FPW
>
>My CONFIG.FPW looks like this:
>SCREEN=OFF
>TMPFILES=D:\LW2LOCAL
>EDITWORK=D:\LW2LOCAL
>SORTWORK=D:\LW2LOCAL
>PROGWORK=D:\LW2LOCAL
>DEFAULT=E:\LW2000
>
>The directory I'm in is LW2LOCAL, and it is where I have specified my temporary files to go. My actual data and reports, etc reside on the network under E:\LW2000
>
>When my app starts, SYS(5)+SYS(2003) Clearly show that my current directory is D:\LW2LOCAL, and SYS(2019) clearly shows that I'm using the CONFIG.FPW in that same directory. Now the wierd part...
>
>Why are my temporary files going in C:\Windows\Temp, why isn't my default directory set to E:\LW2000 and why when I FOPEN("CONFIG.FPW") in my EXE (which shows SYS(5)+SYS(2003) pointing at my D:\LW2LOCAL directory) - I am NOT getting the CONFIG.FPW in that directory!
>
>What is going on?
>

Are you trying to run this under the development mode? If so, the CONFIG file used when starting up the development mode executable is not what you expect, and I'd think that you've got your default location for the temp files set to your Windows\Temp directory. Try the following:

Create a shortcut to start VFP in the correct location. Your comand line should look like:

c:\SomeRandomPath\VFP.EXE -cD:\LW2LOCAL\CONFIG.FPW MyApp.EXE

Make sure that the starts in directory in the shortcut specifies D:\LW2LOCAL

See if the program behaves as expected and go from there
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
Répondre
Fil
Voir

Click here to load this message in the networking platform