Alexander,

The question was triggered by the following extract:

The current version of PhDbase is multi-user, but it is not reentrant. This means that PHDBASE.V30, PHDBASE.V50 or PHDBASE.FLL may not be used in multiple instances of FoxProW or VFP on the same machine (but the same .V30, .V50 or .FLL may be used on different machines).
ances of FoxProW or VFP on the same machine (but the same .V30, .V50 or .FLL may be used on different machines). If you need to run multiple instances of VFP or FoxProW with PhDbase, simply create a copy of PHDBASE.V30, PHDBASE.V50 or PHDBASE.FLL under a different name and load the "different" library under the second instance of FoxProW.

Since product is unsupported ,I am not sure, what was meant by that. Presumably, if we manage to run almost simultaneous searches from different instances we may encounter reentrance problem.


>Michael,
>
>FLL is a kind of DLL and you shouldn't have any problems with simultaneous use by several applications. Only program code and read-only data are shared by applications. Each process has its own copy of variables within FLL.
>
>>Is my understanding correct that FLL is loaded only once ( when we issued
>>Set library to certain.fll ) and the same copy in memory is used by several different applications.
>>If FLL is not reentrant what should I do to avoid sharing ? Would having different names per application for FLL be enough to load it again for each application.