Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
CurDir() is not always correct.
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00001661
Message ID:
00001663
Vues:
44
>Hello,
>
>This is an FYI posting that gave me a headache
>trying to track down. Perhaps this is basic, but
>it may come in handy for some of you. If you use
>the CurDir() function to determine the path of the
>executable, it will only return the directory
>specified as the working directory (in the
>properties for the icon in the Program Manager)
>and not the actual correct directory. At least
>this seems to be so for NT 3.51. Does anyone know
>of a way to specify the working directory from the
>setup application? My users can barely comprehend
>the idea of making or modifing icons in the
>program manager <g>.
>
>Scot.

Believe it or not I found the best way is through an INI file or Win Registry edit. Relying on functions for app startup is not 100% reliable.

Tom
Tom
--------------------------------
Tom O'Hare
407-299-4268 -- tom@redtile.com -- http://www.redtile.com/
Independent Programmer Using Visual FoxPro, Visual Basic & more...
Operations Manager -- Virtual FoxPro User Group (VFUG)
http://www.vfug.org/ -- tom@vfug.org
President -- Central Florida FoxPro User Group (CFFUG)
http://www.redtile.com/foxpro/
Universal Thread Most Valued Professional (MVP)
http://www.transformation.com/foxpro/
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform