Hi Cy,

Well with Web Connection you can get away with the smalledst 5 user SQL license in most scenarios ($1499 retail)

However, I'm not sure that you are in fact allow to do this for a Web app. If I remember right MS has a special Web license that is required for Web applications even if there's a single connection to the database. I don't know if this has changed recently but was that way a couple of years ago. I think (but am not sure) that Web apps now must use the per processor licensing scheme (which really sucks as it's $$$)

Hopefully somebody who's read through the many confusing license agreements can clarify...

+++ Rick ---

>>Hi:
>>
>>I'm new to WC. My first project will be to convert a VFP\SS app to web. The question that comes to mind is how do I handle connections and licencing?
>>
>>I was thinking of having user login at app startup, then store ID to session variable. On each trip to database I would use contents of session variable to do a string connect, then use handle returned from string connect in a SQLEXEC() call to perform some database operation. Is this how its done? If not, what is best way to do this?
>>
>>Also, we have 50 licences. If connection is only used for duration of query, the 50 licences should support many requests.
>>
>
>
>SQL Server licensing is the same for a web based app, as for a normal client server app. You either must processor license the SQL server, or have a license for each machine that will connnect to the data through the app.
>
>The connection handling thing would probably only work if you run only a single copy of the app on the server. However, you usually will want to run at least a couple of them. This said, you may need a connection for each copy at least. Actually you probably only need a single connect per copy of the engine, and I would use either a global propery that is not going to go out of scope, or a public variable.