Effect of many instances of Access

[pinkdatabase]

I have a MS Access 2003 database which is shared over a network. I have split the database to an application MDE file and a data MDB file (backend) each sitting on the server. There is only one version of the application mde which is located on the server. The is no application or data on the user machines.
When a user X logs into the database on Machine 1 I capture the UserID on a login form called frmSTART. The user selects their name (and hence UserID) from a list in a combobox (user) control and then enters a password. The form frmSTART is then hidden for the remainder of the session.
Throughout the rest of the database I use the UserId value in the user combobox on frmSTART (hidden) for all my permissions, change management and other functions that identify who the user is.
The question is - if another user Y logs on to Machine 2 allocating a different UserID to the user control on frmSTART will this impact on the instance of Access being used by user X on Machine 1 and hence on all the procedures that look for the UserID on the frmSTART.
How does it work with different instances of Access open
I am developing off site on a stand alone machine so cannot test this on a network.

Thanks in advance

 

[DCrake]

Although you have split the app to FE BE each user must have their own copy of the MDE on their machine not sharing the login point on the server. As one user logs in they are overwriting the permissions of the previously logged in person.

 

[pinkdatabase]

Thanks David

I was hoping not to have to do that as there are issues with deployment but maybe it is the best solution as I believe it will speed the application up as well over the network

Greg

 

[boblarson]

Thanks David

I was hoping not to have to do that as there are issues with deployment but maybe it is the best solution as I believe it will speed the application up as well over the network

Greg

Deployment shouldn't be an issue if you use an auto updater. I have one available for free on my site that I wrote and Access MVP Tony Toews has one available too.

 

[pinkdatabase]

Thanks All
Have decided to deploy the fe to each of the workstations and will have a look at the tools for deployment you mentioned
Greg

 

[G37Sam]

What I did once was, have MS Access write the username on a text file on the local computer's hard disk (c:\login.txt for example)

User Permissions are then checked by reading that file

Again, not the best way to do things but if you're already there and stuck, this should work

 

[pinkdatabase]

Another way I was developing is to read the machine name and system user name and rely back to those two parameters to identify my user. But this meant it would be difficult for me to use an Access query to identify my user without a lot of code. So with the fact that deployed fe is faster then we will just have to overcome the deployment problems which relate to personnel and procedures rather than database issues