Thanks for the advice John. Your two suggestions are also considerations I need to start researching.

A couple of questions:

1. Is Web Connect strictly a VFP tool?
2. For your second suggestion are you referring to COM and ASP?
3. I've looked at some technical articals from msdn.microsoft.com on ADO, 3-tier apps with VFP, and MTS. Do you have any other suggestions for technical articles, whitepapers or courses that might help me get my head around all of this?

>VID is essentially a dead product. It's feature set will be incorporated into VB and VC in the next version of Visual Studio..
>
>However, let us suppose for a moment that the above is not going to happen..
>
>VID is a pig. The idea is good - taking the event-driven programming model to the web. The execution of the idea - in a word - sucks. The Jscript code that gets created is both of bad quality and is extremely buggy. Ever try to debug a VID app? Sure, the theory of tracing though code exists. Getting it to work is another story. For 70 dollars (US), you can buy Allaire's Homesite HTML Editor and have a superior editor to what you will find in VID.
>
>Further, VID apps do not scale all that well. The whole idea behind the Design Time Controls - the very thing that is supposed to make VID easy to use - begins to crap out after 20 or so users. Again, the underlying code of DTC's is very poor.
>
>My advice...
>
>One option is go use Web Connect
>Another is to be component based - and use script as glue. Here, you can use any editor you want - including home site.
>
>Good luck..
>
>
>
>
>
>
>>We are starting to look at Web enabling certain existing applications and all new applications and are starting to look at VID.
>>
>>I would appreciate any comments and experiences people have had using VID to determine if this is a good direction to go or if we should be looking at something else. TIA