Multiple sessions by same user

[TESA0_4]

Hi,
I have developed an app that every employee (200+) is allowed to have
read-only access to. Only a few employees have particular permission levels
(and personal usernames) that allow them to edit, create and delete data.
At anyone time, I only expect a maximum of 10 users to be logged on for a
session and only 2-3 or those users will have permission levels that allow
them to actually modify data.
I have created a generic username called READ to allow anyone to login and
gain read-only access to the data.
It is only early days in the life of the application.
Am I going to run into problems if, say, 10 people were to concurrently log
on using the generic READ username?
Thanks in advance for any thoughts you might have.

 

[katy]

Hi,
I have developed an app that every employee (200+) is allowed to have
read-only access to. Only a few employees have particular permission
levels
(and personal usernames) that allow them to edit, create and delete data.
At anyone time, I only expect a maximum of 10 users to be logged on for a
session and only 2-3 or those users will have permission levels that allow
them to actually modify data.
I have created a generic username called READ to allow anyone to login and
gain read-only access to the data.
It is only early days in the life of the application.
Am I going to run into problems if, say, 10 people were to concurrently
log
on using the generic READ username?
Thanks in advance for any thoughts you might have.

 

[Tom Wickerath]

Hi Tesao,

Am I going to run into problems if, say, 10 people were to concurrently log
on using the generic READ username?

No.....if you design your application correctly. For example, do not allow
users, including READ only users, to open forms that are bound to hundreds
(or thousands) of records, as this can place too much load on a file server.
A common error I see is to open forms or reports (or combo / list boxes on
forms) to a boat-load of records, and then the user applies filters after the
fact. Too late from a performance standpoint.

Make sure to split the database, installing a copy of the FE on each user's
local hard drive. Establish persistant connections for each user, etc. etc.

I have summarized these ideas in the paper shown below:

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm

Of course, one needs a good solid network as well.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

 

[TESA0_4]

Thanks Tom for taking the time to reply. I'm encouraged because I have
already done all the things you suggest so hopefully I have a robust solution!

I will check out you web link for further tips.

Thanxs