>I am curious,
>Has anyone here actually used VFP to build a MTDLL and hosted it on their web site.

Yes, but why do I feel like I am walking into something here. :-)

>If so can you tell me what the site does

It is a regional application for biomedial engineering. Biomed is the dept at a hospital that fixes all of the complicated medical equip. The apps tracks
- devices
- device maintance
- schedules preventative maintenance
- tracks non device work done for clinical areas (training, incident investigation...)
- time management
- stores faqs of common problems with devices
- stores info about customer service reports to areas
- resonably flexible reporting to Excel and PDF
- staff sign in/out board
- device sign in/out board
- parts database

> and point me at the site.

Sorry, it is a private site that requires a username and password. Let me know what you would like to know about it.

>I want pure COM architectures not a west wind hosted site. I know Ricks's stuff works fine for this I just want to see a real site with a VFP-COM object called from ASP or ASP.NET (or some other technology capable of calling COM objects)

We don't use West-Wind. Our architecture is 3 tier.
- UI is ASP.NET written in C#
- biz tier is Visual FoxPro 8 COM component
- data tier is Visual FoxPro tables
- data is passed between tiers using XML which is freakishly fast
- data is manipulated in the UT tier with ADO.NET datasets
- reporting is done asynchronously by having an custom built report server (just an EXE) that reads a queue (a FoxPro table) and processes requests from it. WWPDF is used to send reports to Adobe. Reports can also be sent to Excel or rendered as graphs using GDI+. Reporting was done using a report server (kind of like how West-Wind has servers)so that the sytem wouldn't be overwhelmed with too many intensive requests at once.

Everything runs on a DUAL Xeon (P4) 2.8Mhz Intel box with a gig of RAM.

Generally I am pretty happy with the system and the speed of the system. One thing I don't like is that a form with tons of controls on it, takes a while to render in ASP.NET.

Will eventually move to SQL Server or MYSQL as the back end in the next 6 months or so, just so that the tables don't need to be packed. Probably will go with MYSQL just to give us room to manoever if technology changes. Will keep Visual FoxPro as biz tier because of the freakishly fast XML handling.