I've been reading Rick's book and trying to learn more about VFP web applications. One bit of info I cannot find: Now that VFP6T is here, is the best way (and simplest way) to implement a VFP COM server to simply use a single-instance COM server as an in-process DLL, creating the server with VFP6T instead of VFP6R.DLL? Or are you still better off using one or more out-of-process EXE COM servers that are generated to use VFP6T instead of VFP6R? Or something else?

Also, has anybody experimented with using ASP and passing objects to a VFP COM object (and back)? Any comments on performance compared to using a pure FOXISAPI approach?

I get *very* confused when I think of generating a persistent ADO recordset in VFP and sending it back to ASP. In particular, if one VFP COM server is simultaneously serving several web connections, how do you keep track of the recordsets that are generated within the COM server? In other words, within VFP how do you keep a recordset persistent and attached to the correct web session when you return from VFP back to ASP and then invoke a method in the VFP server again?