Many of these problems are a result of lack of documentation from Microsoft and some kind of list of best practices to use with mtdlls. What I've tried to do with ActiveVFP is to have it all in that code and the documentation so the developer doesn't need to worry about it. A lot of it came thru trial and error over several years. For example, the use of COMRETURNERROR is a must for any mtdll, but you won't really find this explained in any great detail in the MS docs. Similarly, the use of COM+ for SQL/MSDE or networked DBF access makes it possible to impersonate a user with network rights so that Data access is smooth and secure, but, these details are not really in a central place other than AVFP. So, what I'm saying is, if it's properly supported, there is not really any problem with this technology and definitely no more than with traditional vfp web development. BTW, PHDBase should work from a COM .EXE which is called from the vfp mtdll. Also,I've gotten Refox to work on mtdlls (as well as timers)..

>> What kinds of major problems did they have if you don't mind my asking?
>
>The CD issue was a big problem for many customers, because AFP 2.x changes to the web directory when a requests comes in to make it easier to deal with pathing. Aside from the usual UI related stuff, we had problems with code that relied on timers. They don't fire in an MTDLL. COM automation failed in many cases, because call backs were not working due to the different event processing loop. We had problems where VFP displayed an error dialog instead of raising the TRY...CATCH handler, for example, when a field validation rule is violated. We had problems with customers insisting on the VFP 7 runtime since their code was written for VFP 6, or because there wasn't a service pack 3 for VFP 8. Think of an MTDLL without TRY...CATCH. We had problems with bugs that only come up in an MTDLL under stress, not in a regular EXE. For instance, when calling a function, VFP suddenly drops all but the first two parameters. When your code says oBizObj.Load( "ALFKI", "curCustomer", 3 ) it's confusing
>if the third parameter is suddenly .F. A lot of third party tools do not work in the MTDLL environment. We had problems with PHDBase and Cryptor, for instance.