>>The combination I think would work best for me is to do Web stuff in LAMP, with VFP being the data pump to crunch and munch the data (and prepare chunks of HTML) into MySql tables.
>
>Well but that still leaves VFP's weak spot in the picture which is its lack of true multi-threading. If VFP is the 'data pump' it still ends up being a server that has to serve multiple requests simultaneously. That's where the rub lies <s>... There are many high end applications that get around this of course, but it's not as easy as sticking an ASP.NET page on a server and firing against SQL server (or PHP + MySql) because of the infrastructure issues.

Um, I meant data pump in a different direction. My pet project would need a lot of data imported, and sometimes offline processed, with the end result being stored on MySql. VFP would do that. Also, huge chunks of preprocessed HTML can be created in VFP and stored (which I was already doing in another project, and it worked smoothly). IOW, any housekeeping that isn't invoked by visitor's click on a webpage.