I'm having a problem with public objects being available for other sessions in a multi threaded dll.
To describe the actual problem;
The MT DLL (built using Microsoft Visual FoxPro) is used as a COM+ for a web based application. On occasions it has been noticed that certain public objects created in one users session is accessible from another users session (as it displays info related to user1 session).
If the public object is not released this can be simulated consistently, which I assume is bcos for user2 the object is not created in his session, but rather uses the un-released object from the other users session,
Is there any reason why this occurs?
Is it a problem with how the component has been created? We have tried creating it as a Library Application as well as Server Application but
this does not seem to solve the problem.
Further we have tried the option when building the DLL via VFP Project Manager after changing the Instancing to Single Use in the Servers tab.
This too did not help.
The DLL is a collection of several visual fox pro classes.
Any help on this would be really appreciated.