>But I am not debating! I am really asking! I have a client now who needs a web solution dealing with SQL Server. I realize that Web Connection is not in the same demand as ASP, but will I dig myself into a hole where the client says, "Hey, I need the program to do this." And with ASP will I have to say, "Well, I don't think so".
>
>And what about fat clients? Can I come close to WC with a VB solution over HTTP? It does not have to be as good as WC, just in the ballpark. Again, I am not debating. I want to know if I can offer this kind of solution to my client.>

I use Web Connection to talk to VFP, Acess and SQL Server. I think developing in WC is an order of magnitude faster than ASP. The VFP debugger is a lot better than what you have to offer in ASP development. Of course, I made a conscious decision to quit putting bugs into my program quite some time ago, so I don't have that problem. Still have some "features" though. If the person buying the app is concerned about what it's written in you may have problems, but if you can demonstrate the ease of development and speed of the application, WC will take you most anywhere you want to go!