John,
Yes, I think the general consensus is to not use MTS unless you have specific reasons to use it since it slows performance somewhat and makes the environment somewhat more complex. Let me know if you need any code or examples for this environment(ASP/VFP mtdlls). We also have some white papers at www.activevfp.com ...
>Dear Those-With-More-Experience-Using-COM-on-the-Web,
>
>We have a single server on the Web and want to give users the ability to query a parts table (and do a small amount of data entry). A subset of VFP data we want to make public will be copied to the Web server daily. We're planning to use:
>- ASP
>- Windows 2000 Server
>- VFP7
>
>The VFP7 component, called by ASP, will return a string of html formatted
>data based on the parameters submitted by the user.
>
>Given this simple scenario and assuming concurrent users, performance, and
>versioning should be considered:
>
>Is COM+/MTS relevant since this is on a single server? Or do I
>simply build a server application and install it on the Web server?
>
>At the moment I'm planning to:
>- Not use COM+/MTS
>- Build a multi-threaded dll
>- Initially use InstallShield to install the dll, tlb, and vbr in a [ProgramFiles] folder
>- Use Regsvr32 to register it.
>
>To update the server with fixes/enhancements:
>- IIS: stop the website
>- Unregister the dll
>- Copy over the new dll, tlb, and vbr.
>- Register the dll
>- IIS: start the website
>
>Many thanks for your sanity check.