Mihai,

In addition, I may suggest an approach that works for me: in SQL Server's logins I've added as users the computer IP adresses. They all share the same password. The actual users have their username and passwords stored into a sql server table. Their access rights are also stored in a sql server table.

The process goes like this: they launch the app, app gets the local ip, compose the connection string using the password encrypted in the app, connects to sql server, if it's ok, shows the login form, user enters username/pwd which are checked against users table and that's all.

Hope this helps.

>Cetin, thanks a lot for your opinions. It helps me a lot because I can see different points of view and apply the best .
>If I use my app to login, then I can use only one user and password to log to SQL. And , also (important), the users can't connect from another Windows application to SQL because they don't know the password to SQL, only the application does .
>
>
>
>Mihai.