Tracking users access & max users in a secured db at same time

[terushb via AccessMonster.com]

What is the easiest way for me to track user access of a secured database...
I have 25 users using a FE database.... what is the maximum number of users
that can be in a database at a time entering in records.... They won't be
editing the same record at the same time, so that's not an issue, however,
they will be using the same form obviously to enter a record... I don't
beleive there is a real issue unless someone trys to edit a record being
edited by another user... isn't that correct...?

 

[John Spencer]

The absolute maximum number of simultaneous users is 255.

The practical maximum is usually more on the order of 30 or so. BUT it all
depends on the design of your database. I've seen databases that work well
with more than 30 concurrent users and I've seen databases that do not work
well with 5 concurrent users. For instance, no one should ever be retrieving
all the records in a table for editing - which means the record source for
forms should be query-based and the query should use criteria to limit the
number of records being returned.

I am unsure of your setup. You mention a front-end, so I am hoping that each
user has a separate copy of the front-end and that users do NOT share one copy
of the front-end.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

 

[terushb via AccessMonster.com]

Hi there John,

First thanks for your assistance ----

Please no laughing -- ;o) OOPS, the users have a Desktop Shortcut to the FE
which is housed one of our network drives and the BE is also on the same
drive... There is one workgroup associated to the FE & BE.
So are you saying what I should do is copy the FE to each Desktop instead of
just doing the right click - add shortcut to desktop... I didn't even think
about that... Please advise... So could I just have the users do right click
copy of the main FE, and then drop on their desktop.. This will not say "Copy
of" on the copied file of the FE name correct --- I did the right click -
copy- and dropped on a users desktop and didn't see "Copy of" as part of the
file name. In doing this I assume since the backend is still associated with
the copy any changes I do to the the BE will also be updated to the copies..
I think I have had a case of SOS (Stuck on Stupid)... I only have 20 users
and we are just in the testing phase... Thanks John for any assistance...
Also, since everyong would have thrier own copy of the FE, how do I go about
easiily making changes to the main BE, and getting that uploaded to all the
Users Copies without having to manually delete and re-copy the new revised BE.
.. Thanks TerriB.

The absolute maximum number of simultaneous users is 255.

The practical maximum is usually more on the order of 30 or so. BUT it all
depends on the design of your database. I've seen databases that work well
with more than 30 concurrent users and I've seen databases that do not work
well with 5 concurrent users. For instance, no one should ever be retrieving
all the records in a table for editing - which means the record source for
forms should be query-based and the query should use criteria to limit the
number of records being returned.

I am unsure of your setup. You mention a front-end, so I am hoping that each
user has a separate copy of the front-end and that users do NOT share one copy
of the front-end.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

What is the easiest way for me to track user access of a secured database...
I have 25 users using a FE database.... what is the maximum number of users

[quoted text clipped - 3 lines]

beleive there is a real issue unless someone trys to edit a record being
edited by another user... isn't that correct...?

 

[John Spencer]

The only changes you should be making to the backend are to the table
structure. That should not be a frequent occurence. Any time you change the
backend structure, you are probably also going to change the front end structure.

Yes, each user should have a copy of the frontend and when you copy that over
to their workstation, the name of the frontend will not change.

I use the following free utility to propagate changes to my users. Once it is
set up, all you have to do is copy the latest version of the front end to the
server. The next time the user clicks the icon to launch the database, it
will copy over the new version.

Tony Toews' Auto FE Updater

This utility will automatically update the Microsoft Access front end (FE)
MDB/MDE/ADE/ADP and associated files from a server to client workstation(s) or
other network locations.

This utility is designed to automatically update the front end and
associated files from the server to the client workstation or
directory on the server. The utility will, if required, create the
directory on the workstation, copy files to workstation, create a
shortcut on the desktop and update registry keys. It will then start
the Access MDE/MDB. If none of this is required the next time you run
this utility then all those steps are bypassed and it just starts the
Access MDE/MDB.

http://www.granite.ab.ca/access/autofe.htm

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

Hi there John,

First thanks for your assistance ----

Please no laughing -- ;o) OOPS, the users have a Desktop Shortcut to the FE
which is housed one of our network drives and the BE is also on the same
drive... There is one workgroup associated to the FE & BE.
So are you saying what I should do is copy the FE to each Desktop instead of
just doing the right click - add shortcut to desktop... I didn't even think
about that... Please advise... So could I just have the users do right click
copy of the main FE, and then drop on their desktop.. This will not say "Copy
of" on the copied file of the FE name correct --- I did the right click -
copy- and dropped on a users desktop and didn't see "Copy of" as part of the
file name. In doing this I assume since the backend is still associated with
the copy any changes I do to the the BE will also be updated to the copies..
I think I have had a case of SOS (Stuck on Stupid)... I only have 20 users
and we are just in the testing phase... Thanks John for any assistance...
Also, since everyong would have thrier own copy of the FE, how do I go about
easiily making changes to the main BE, and getting that uploaded to all the
Users Copies without having to manually delete and re-copy the new revised BE.
. Thanks TerriB.

The absolute maximum number of simultaneous users is 255.

The practical maximum is usually more on the order of 30 or so. BUT it all
depends on the design of your database. I've seen databases that work well
with more than 30 concurrent users and I've seen databases that do not work
well with 5 concurrent users. For instance, no one should ever be retrieving
all the records in a table for editing - which means the record source for
forms should be query-based and the query should use criteria to limit the
number of records being returned.

I am unsure of your setup. You mention a front-end, so I am hoping that each
user has a separate copy of the front-end and that users do NOT share one copy
of the front-end.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

What is the easiest way for me to track user access of a secured database...
I have 25 users using a FE database.... what is the maximum number of users

[quoted text clipped - 3 lines]

beleive there is a real issue unless someone trys to edit a record being
edited by another user... isn't that correct...?

 

[terushb via AccessMonster.com]

Hi there John,

Yes the only data I have in the BE are tables.... and those I only update
when I need to add a new employee or client to the client or employee table
etc... I have ocassionally had to add a new table based on the type of Data
management is wanting to track.. But I have had to make changes to the Forms
and/or Reports or even once a while a query in the BE, and that's why I was
concerned about the users being able to access the most recent/revised BE
(this is an often occurance)....
I will see if I can use Tony's Auto FE Updater Utility... I think I can do it.
..
So it sounds like what I will need to do is have the users delete their
shortcuts on their Desktops to the Main FE, and then have each of them do a
right click on the Main FE, and select "Copy" and paste it to their desktop...
I will try the Auto FE Updater Utitlity, hopefully I won't mess up... Any
suggestions downloading and implementing the Auto FE Updater, since I am a
hands on Access Developer... Needs of the business... LOL! Hopefully when
budget permits I'll get to go to some ACCESS training...
But I so have FileMaker Pro & 8 Developer Background so this is another
Database App I am loving learning as I go... So anything you can share would
be greatly appreciated... By the way, Thanks so much for your time, I am sure
you are quite busy.... Your New Access Admirer, TerriB

The only changes you should be making to the backend are to the table
structure. That should not be a frequent occurence. Any time you change the
backend structure, you are probably also going to change the front end structure.

Yes, each user should have a copy of the frontend and when you copy that over
to their workstation, the name of the frontend will not change.

I use the following free utility to propagate changes to my users. Once it is
set up, all you have to do is copy the latest version of the front end to the
server. The next time the user clicks the icon to launch the database, it
will copy over the new version.

Tony Toews' Auto FE Updater

This utility will automatically update the Microsoft Access front end (FE)
MDB/MDE/ADE/ADP and associated files from a server to client workstation(s) or
other network locations.

This utility is designed to automatically update the front end and
associated files from the server to the client workstation or
directory on the server. The utility will, if required, create the
directory on the workstation, copy files to workstation, create a
shortcut on the desktop and update registry keys. It will then start
the Access MDE/MDB. If none of this is required the next time you run
this utility then all those steps are bypassed and it just starts the
Access MDE/MDB.

http://www.granite.ab.ca/access/autofe.htm

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

Hi there John,

[quoted text clipped - 42 lines]