Hi!

Because VFP or VB COM objects under MTS are never full multi-threaded, the same COM object code will never run simultaneously in different threads. If they run, they will be completely separate COM objects with their own working environment, so you can feel free to use default data session. Private data sessions are useful here only in case you do several complex calculations inside of the COM object that requires careful environment controlling for each one. I never used this in MTS COM objects...

>I have been building MTS/COM objects (compiled as MTDLLs) for use with IIS for a while now, but have never used the session class in terms of managing the tables the object used. Does anyone see a need to always use them for COM objects? I am now thinking that I should do something with private datasessions always, fearing that a heavily-used DLL will step on "itself" when doing a lot of CRUD.