Thanks for the info - I wish someone would do a write-up of your project so we can all see how well it works. I'd be happy if we could 'unload' the vfp dlls that have been called from .NET which could then be totally automated and thus transparent. I believe the more vfp developers looking at projects like this the more likely these types of wrinkles will be smoothed out...

>>My point is that I wouldn't bail on VFP for developing a web browser based product/project. It really is not that hard to put one together and re-use your vfp application logic on the web. Doing this would possibly get you new business and allow you to keep using VFP. Using VFP Business Objects that can be called from Web or Desktop makes a lot of sense here if it is possible...
>
>That's exactly what we have done. VFP for the biz tier and data tier. Works great. The one feature I want though are VFP DLLs that I can copy onto a running webserver without have the register them and stop/start IIS.