There are some things regarding what you might call "state persistence" that I'm trying to understand better with VFP MTDLL COM objects. Here the objects are being instantiated by an Active Server Page application. For example:

- When a USE command is executed within a method of a MTDLL COM object, does the "used" table remain open even after the object is destroyed? What exactly is the persistence of open tables? What about open files (e.g., with Fopen)? Should all tables and files be explicitly closed in the object's Destroy event?

- What about persistence of:
-- Set PATH?
-- Set PROCEDURE TO?
-- Caching of FXP files. for example: Do xxxx where xxxx is an FXP file

I also need to understand better just what is the scope of the data structures that hold this state-related information. For example, assume 2 threads are initiated (two users come to my web site simultaneously and the web page they request instantiates the same object). If thread A opens a table, will it remain open in thread A until that thread is terminated (I think I'm asking if state-related info like open tables is stored in static storage local to the thread). Would thread B have no visibility of the table being open?... except that if thread A got to it first, then an attempt by thread B to open the table exclusively would fail, no?

And for that matter, just when do threads actually terminate? Who decides?

Any info much appreciated. Thanks!