Be careful that multiple Automation servers in a single in-process. In this case, it's possible that the Automation servers can affect each other by sharing PUBLIC memory variables, setting the same SET commands, and so on if they reside on a common thread. dll share the same main Visual FoxPro run-time library. Multiple Automation servers, created with OLEPUBLIC clause in the DEFINE CLASS command, in a single in-process. dll files use the main Visual FoxPro run-time library because the clients load in separate processes. In this case, both Visual FoxPro in-process. dll files without the run time being renamed. This means that two separate clients, each running in their own process, can load two different Visual FoxPro in-process. Visual FoxPro run-time libraries are renamed only for in-process. dll server, a situation where both share the same run-time library from the same process.

This can also occur with a Visual FoxPro. A copy of the Visual FoxPro run-time library is renamed to MyServerR.dll and is loaded into memory to service the in-process. dll.įor example, suppose you call an in-process.

The main Visual FoxPro run-time library is assigned a name based on the name of the in-process. dll file already has exclusive use of the main Visual FoxPro run-time library, a renamed copy of the main Visual FoxPro run-time library is created on disk and loaded into memory for each in-process. dll file that is called first has exclusive use of the main Visual FoxPro run-time library.

The following rules determine how in-process Automation servers use the main Visual FoxPro run-time library: Instead, each in-process Automation server uses a separate instance of the main Visual FoxPro run-time library. The main Visual FoxPro run-time library is not shared by all the multiple in-process Automation servers (.dll).

Visual foxpro version 9 runtime library