Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Project Options Home Directory
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Divers
Thread ID:
00028529
Message ID:
00028539
Vues:
53
>>>>>I have my project and all of its files on my local D
>>>>>drive. I set up my development environment to the
>>>>>local drive to modify and build my apps and exes. Once the apps and exes are built then they are moved to our novel server for access by the department (K Drive). My question is this , the project options dialog has a button labeled HOME DIRECTORY, what is the purpose of the value stored in there and how does it relate to the apps or exes that get created.
>>>>>
>>>>>Bret
>>>>
>>>>It relates to 'project' tree. To handle 'production' tree you have to set path programmatically using e.g. database path stored/modified in some configuration table.
>>>
>>>What I have been getting is that all of my programs/report/etc.. are
>>>included in my project when I build it. When a user executes my app/exe on the network and they dont have a D drive (HOME DIRECTORY in project) they receive and error, if the do have a D drive even if it is a CD drive they receive no errors. What is it looking for on D when a user runs my app.
>>>
>>>Thanks for responding so quickly....
>>
>>Probably it will help. It looks like you either hard-coded 'D' in some place, or you have problem with DataEnvironment. Open some form where you use DE and check Database property. It can include D, if you use 'project' data located on this drive. To avoid this problem you can change all these properties manually, but the better way is to write common method which will reset Database properties in BeforeOpenTables events.
>
>No D hard coded any where, and this is FoxPro 2.6a for windows no DE.
>
>When I changed the HOME Directory to C:\ and packed and saved the project. The HOME DIRECTORY option for the project showed C:\WINDOWS even though I picked C:\. I distributed the app/exe to the novell network and now the app/exe works fine.
>
>My conclusion is that everyone had a C Drive so when the app went looking for a C drive enven though there is no coding of C drive in any program, the app found one and then continued.
>
>Bret

I am sorry. I didn't notice that this is 2.6.
Edward Pikman
Independent Consultant
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform