Thank you Rick -
It is a "Custom" class. I am learning there are many nuances to class structures. For example I think I noticed that class properties assigned with the notation cDataPath="C:\Inetpub\Scripts\Data\" seem to only fire properly when scripted after the methods (at the bottom of the definition).

The class methods basically do the housekeeping and then call a udf outside the class, for example

define class myclass as custom olepublic
procedure login
lparameters lcFormsVars, lcIniFile,lnReleaseFlag
local lcOutput
set path to (this.cScriptsPath)
sys(2336,1)
with this
lcOutput=GetLoginReturnPage(lcFormsVars,.cDataPath+[login_dbf],;
         .cDataPath+[info_dbf],.cScriptsPath)
endwith
sys(2336,2)
return lcOutput
endproc
enddefine

Most of the time the dbfs are opened as noupdate. Is the issue related to opening the dbfs with "use"? I had hoped to do it from the [custom] class init. My early attempts seemed problamatic. Most of the transactions are in and out. A few methods may call more than one udf [and require four (five at most)dbfs] before returning script or a url to the browser.

Could you recomend a way to "use" the dbfs such that they are available as workarea handles to the internal class methods, as well as the [external] udf requests, throughout the thread? Should the "used" dbfs be closed?

This is an MTD. I was talking with Michel about error methods. It seems foxISAPI (the client) services the exceptions. Is this the case? What can the COM's error method do to assure [augment?] a proper routing and error reset?

Is lnRelease important in MTDLL?

Thanks
If you derive from Session anything you do in the class will be isolated to that class because it is - surprise - a Session object. If you use Custom you shouldn't have this problem (although you have to do more setup potentially). Note also that you see open tables only through the same object. Another object may (or may not) be loaded on another thread.
>
>+++ Rick ---