New to access. Front end question

Brewsi

New member
Local time
Today, 22:23
Joined
Mar 2, 2016
Messages
9
Hi there,
I'm quite new to access and have built a very basic database. That is the back end has one table and the front end has One form. I want to roll it out to a department at work. I don't have the facility to make each user in the department a copy to save to their machine.

My question is how many users can use the form in the front end at the same time? or is there a better way to achieve a multi user front end without creating multiple copies of the fe.

Thanks in advance for your help
 
1 FE per person. Just email to them.
If you only have 1 PC, then only 1 person can be in it.

You might get more to use the 1 copy, but you'll get an error soon.
 
I thought as much but was hoping I could get away with it. Thanks a lot for your reply
 
one last question. Is there a limit on the number of front ends that can be used?

Thanks again for your support.
 
only limited by the number of open file handle that a server can have. somebody correct me if im wrong, i think 10 on xp, 20 for win7 and up, that is simultaneously. create a shared folder and copy the fe there. then each user can copy this fe. don't let them run on the shared folder.
 
Sorry to be a pest just one last question on the back of that.
Is there a limit to the amount of copy front ends that can be used? For example if I emailed out a front end to everyone is there an amount that can be used simultaneously?
 
see my post, if the be is on window server, i think its unli.
 
in theory an unlimited number of users can use a database concurrently.

in practice, concurrent heavy use can cause performance to dip. A "normal" database such as an "office acounts" database is relatively light in use, and can probably easily manage 20 users concurrently, and probably many more. At some point users demands on data start to impinge on performance

in theory multiple users can all use the same copy of the database at the same time. That's the way it is designed. In practice we find it can lead to corruption and recommend against it, but you can try it anyway. Your database sounds simple and may not error.

One thing you can't do if multiple users are using the same copy of a database is amend temporary data in a local table - as all users will then see the same amendment.





You also ought to split the database so the data tables are in one database, and the forms and queries are in another. You say you have done this.

I don't have the facility to make each user in the department a copy to save to their machine.
Of course you do - that's a standard part of access.

maybe the best procedure is to try it on a shared basis, demonstrate it is worthwhile, and then explain how you need to improve it to ensure it is more resilient.
 

Users who are viewing this thread

Back
Top Bottom