is there a limit to number of users opening an Access database?

[train2]

Hi everyone,
I heard a rumour that there is a limit to how many people can open an Access database at any one time - is there any truth in this? Unfortunately I can't check this out right now, because I'm working from home.

My database is very basic - I have no security set up yet, and just let everyone enter their own data and whenever they want. Is there any problem with this approach?

cheers,
jr

 

[JJOHNS]

I've dealt with this question before. In training classes, I've had as many as 16 users in a database at one time. I also work with a database now that generally has at least 12 users in it at once every day. They tend to be slow sometimes, but they work.

The rule seems to be that the more users you have in the database at once, the slower it runs, but I don't really think there's a set limit to the number of users who can be in the database at once.

 

[SgtJarrow]

Train2,

If my memory serves, the limit to the number of users is 255....I am not 100% positive, but for some reason it seems right to me...

Now, about your "free flow" entry....this approach WILL ONLY work if you don't care about the data....Memo fields are free flow fields that can store in the neighborhood of 65K characters....all other fields are a regimented, structured format of some kind. And they should be kept that way. So, your users should not have "free" access to your data....I am not saying you must force them to do certain things at certain times and enter everything one way....but you should have some tight control and structure to your design. This will make queries, data entry and retreiving, and reporting much simplier.

That all being said, you just need to step back and think about the users and the data. If the users are fairly experienced, you may survive. If the data is completely free flow, you may get by. But if these were the case, then why are you doing the development and not the user creating his/her own db for recording......My suggestion is make as much of the database as structured and rigid as you can get away with....

****************************
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Albert Einstein)

Robert L. Johnson III
MCSA, CNA, MCP, Network+, A+
w: robert.l.johnson.iii@citigroup.com
h: wildmage@tampabay.rr.com

 

[train2]

Thanks for prompt responses and ideas.

Basically, as I had to get something up and running quickly the only security I have is running the Switchboard with limited options for data entry and viewing.

If my users (all teachers, and mostly IT-semi-literate) know that they can activate the real window using Shift+open, and if they want to corrupt the database then I'm stuffed. But then, how many teachers will want to screw up a database that's making their life easier. And you'd have to be very unlucky to mess something up by accident.

The big picture - I'd love to set up security, and create workgroups for teachers so they have access to view and enter data only for their classes, but that's beyond me at the moment. I've just managed to capture the network username, in the hope that I can use that as a basic query variable.... but then there are cases when some teachers will want to update the grades for their colleagues classes (because other colleague is IT illiterate, or away sick - both a distinct possibility!)... so you see, I'm still thinking about ways to do all this type of stuff.

thanks for help,
jr

 

[mswilson16]

To answer your first question, I think 255 is the "official" answer. I've had 25 or 30 concurrent users, with no problems, and I wouldn't be afraid to go beyond that point, assuming the database is set up properly.

You should split your database - front end on the local comuters with the interface, back end on the network with the data. That will make it much more stable, and reduce the chance of corruption of data.

I think you need to implement security. To implement security, you need to follow all the steps correctly.

There's a security FAQ that should lay it out pretty well for you. The basic steps are:

1. Create a new workgroup using WRKGADM.EXE. Don't just make a copy of System.mdw.

2. Join the new workgroup.

3. Create a new user name for yourself, and set a password for your user name. Put your user name into the "Admins" group.

4. Remove the default "admin" user from the "Admins" group (leave them in the "users" group).

5. Open your database and run the User Level Security Wizard. This will make a secure copy of your database without changing the original.

6. Open the new, secure database, and set up your user and group accounts. If you don't want the default user to have access to your database, set up a new user group, and remove all permissions from the existing user group.

This is the condensed version of Access Security. I recommend you read the instructions so you understand it before you implement it.

 

[GDGarth]

For some reason, the last post by me was attributed to "MSWilson". How does that happen?

 

[SgtJarrow]

GDGarth....

This happened to me in the past....I contacted Tek-Tips about it and was told to empty my cookie folder and log back into Tek-Tips.....it is related to a corrupted cookie.

****************************
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Albert Einstein)

Robert L. Johnson III
MCSA, CNA, MCP, Network+, A+
w: robert.l.johnson.iii@citigroup.com
h: wildmage@tampabay.rr.com

 

[train2]

Thanks for response on security. I've already done a lot of reading up on workgroups and rights etc. I have great plans to do this security thing etc. but i already did a previous post on the fact I can't find wrkgadm.exe - even after re-installing.

I need this database for monday, so i'm going to have to go with a rather unstable version.... it's replacing a shared spreadsheet that had millions of problems, so i know although this isn't perfect, it's a better solution.

i've played around with the security wizard and it looks like the same screens that wrkgadm.exe has (i've got screen shots in my book) - but as I am unsure about the whole thing and time is tight, i've got to just go ahead with inbetweenie solution.

thanks for all your replies (wilson, johnson, garth etc!)

 

[SgtJarrow]

Train2...

If you send me an email to my work address below, I will send you a sample databse with something you may find useful. For the most part it is secure....without using access security. The general user, and probably some advanced users, will have a bit of difficulty gettign into the code and all with this. It doesn't provide any way to secure the data from certain individuals, but you can almost definitely keep anyone from accessing the table/forms/code directly and messing with stuff.

****************************
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Albert Einstein)

Robert L. Johnson III
MCSA, CNA, MCP, Network+, A+
w: robert.l.johnson.iii@citigroup.com
h: wildmage@tampabay.rr.com

 

[train2]

Thanks for the example db. It's fine for starters and just tightens up things a bit - before i had just the switchboard being displayed, so now adding the disable F11 and Shift will make it even tighter.
Thanks.
jr