>I'm in the thick of things the same as you, developing a web application using VFP tables. I've decided to go this ASP, ADO, OLE DB route for several reasons. I have my tables all in the same directory. One connecton to the directory for each recordset.open "..", strProvider using the same handle works really well. I also write/update/store using the same connection. I use a command.commandtext, command.createparameter(), .parameter.append(,,,,) and command.execute to write my data. Thus far I've had good success to the FoxPro tables. I use JavaScript on the client side and ASP on the server side (IIS).
>
>I'd be interested in any specific additonal problems you might be having. I'll post any problems I encounter as well.
>
>I've purposely stayed away form com objects, although they work really great.

Be careful when you load the web site. Rick Strahl pointed out in a recent thread that the VFP ODBC driver is single threaded. Even though you are using ADO, you are using the VFP ODBC driver because there is no OLE-DB provider for VFP. You won't have that problem with COM objects.

Also, you are mixing the business logic and data tiers. This will make the site more difficult to maintain. Read up on Windows DNA (www.microsoft.com/dna).