>>I use a connection string (SQLSTRINGCONNECT())...
>
>One more question: I use SQLconnect(), and never figured out what is the (difference) advantage of using SQLstringconnect(). Also, I did some experimenting with "dsnless" connections and didn't figured out the advantages. As you can see I'm a rookie in the backend field.
>
>I really would like to jump over the "deployment issues" my client is *also* imposing to client/server (they want, from now on, just web based apps) apps. One of their arguments is having to configure datasources in each user's PCs. If SQLstringconnect() or dsnless connections could overcome that issue, it would be one less.

SQLstringconnect() creates the connection string in code, so you do not need to create a DSN in every workstation. It makes deployment and future changes much easier.

But if they want just web based apps, then you have another challenge. As long as they accept VFP middle and/or front ends, the back-end is fairly easy and very powerful with SQL Server. If they want a web-based front-end then you have to change your architecture and make VFP run in a web-server, producing HTML code to be sent ver HTTP (easily done with a framework like web-connect, afppages or others). If they don't accept VFP then you'd have to change to a different language entirely, like ASP.Net+C# or VB.Net, or old ASP+VBS, or Cold Fusion, etc.