Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Effect of Set Path and ClassLibs at RunTime
Message
De
25/03/2015 08:52:47
 
 
À
25/03/2015 06:01:40
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01617224
Message ID:
01617241
Vues:
55
Fernando --

Thank you very much for your reply. That was pretty much what I was considering, but had wanted not to try it out if it was a clear dead end.


>>Does Set Path and ClassLibs have the same effect at run time as during development?
>>
>>I have a single EXE which will be used for each of the few countries where we have offices. The EXE is almost identical for each country, but not quite.
>>
>>For each country, I have a single folder that contains files specific to that country. These will be the same file names as for other countries.
>>
>>During development, I can simply use Set Path (for forms and PRGs) and Set ClassLib (for VCXs) to switch between countries.
>>
>>Does this work the same at run time as well? I understand that I will have multiple files with the same name in my project, and multiple classes with the same name and am wondering, before trying this out, whether it will work.
>>
>>Thanks in advance; it's been a while since I've been here.
>
>Hi Jim:
>
>Yes, SET PATH and SET LIBRARY work well at runtime.
>
>For the Libs by Country y give you an idea, that may be useful to you:
>
>- You can use a naming like "library_us.vcx", "library_cn.vcx", and the like, and inside your program you can detect or use a config file for the country, then you can SET CLASSLIB TO "library_xx.vcx" ALIAS LIBRARY, so your program can use this alias "library" for all country specific classlibs. Another example: "lib2_us.vcx", "lib2_es.vcx", "lib2_cn.vcx" can be aliased all with "LIB2"
>
>- For the procedures is easier: Just SET PROCEDURE TO PROC_CN.PRG using the neccesary country, because all internal procedures and functions will have the same naming anyway.
>
>This way you can have all country libraries together in Development in the same project, and can ease their maintenance.
>
>
>Best Regards.-
Jim Nelson
Newbury Park, CA
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform