ISV using SQL Authentication and a small concern

Hi,
I am an independent software vendor and my app will be deployed on users machine, it will use msde for db needs on clients machine. I am using sql authentication and my app will be connecting to the database using a fixed username and password always, fo
r e.g. sa as user and "myPassword$2" as password. (I know I know that this is not 100% great, but we want to keep things very very simple but dont want windows authentication)
Now, please imagine this situation:
a) small office environment
b) My app installed on three machines.
c) database on 4th machine
d) all 3 users running my app on their individual machines and talking to db.
my concern is, will this scenario work, I mean no matter who the user is, my app logs into msde using sa and "myPassword$2", so will MSDE allow 3 users with same logins to access database at the same time.
Looking forward to hearing from you..
Thanks
Hello,
It is working correctly, but if you want to have some security (for example
a part of the program is not enabled if a user is working on another part,
you will have some problems.). For example, if user 1 has a crash, the
program will still believe that user 1 is still connected. Unless you lock
the tables...
Marc Allard
Allcomp
"dev" <anonymous@.discussions.microsoft.com> a crit dans le message de
news:3C66C1B4-CD85-4473-8B9C-9BF40E84853F@.microsoft.com...
> Hi,
> I am an independent software vendor and my app will be deployed on users
machine, it will use msde for db needs on clients machine. I am using sql
authentication and my app will be connecting to the database using a fixed
username and password always, for e.g. sa as user and "myPassword$2" as
password. (I know I know that this is not 100% great, but we want to keep
things very very simple but dont want windows authentication)
> Now, please imagine this situation:
> a) small office environment
> b) My app installed on three machines.
> c) database on 4th machine
> d) all 3 users running my app on their individual machines and talking to
db.
> my concern is, will this scenario work, I mean no matter who the user is,
my app logs into msde using sa and "myPassword$2", so will MSDE allow 3
users with same logins to access database at the same time.
> Looking forward to hearing from you..
> Thanks
|||Hello, (sorry I was in hollidays)
For example, in our program, when a user is working on a project (Project 1)
, any user can enter a new or a position in Project 1, but no other one
modify the project.
Another user can work with project 2 without any restriction so we can not
lock the full table. We had to write a column str_Wholocked on the Project
table to know that the a specific project is locked.
The problem is that if a user crash, he will not free the wholocked field so
you have to know if a user that has locked a fiel is still connected or not.
To make it, when a user connect in my application, I write his connectionID,
login_time... on a table. After that, I look at all the users connected. If
they have a login_time or connection ID different than the one on my table,
it mean that they have crashed so I can free the wholocked field. I make
this test for every connection and every access to something that can be
locked.
PS : I hope that I am clear enough, if not, please tell me what you don't
understand.
"dev" <anonymous@.discussions.microsoft.com> a crit dans le message de
news:765961A8-8196-4B6F-B87A-228DDB63F1F9@.microsoft.com...
> Allcomp please elaborate my what you mean by saying "but if you want to
have some security (for example
> a part of the program is not enabled if a user is working on another part,
you will have some problems.)."
> Thanks
sql