Multi-Users

I am creating a database which will have Multiple concurrent (simultaneous) users (up to 10 people). I have never done this before but I have read there is a Front end and a Back End. Is this something I need to do at the beginning of me building the database or can I do at the end? AND How do I take my database and create the Front End/Back End?

Hi Starnheavn,

Creating 'FrontEnd' and 'BackEnd' is nothing but splitting the Access file into two seperate files, one file holds all your Forms, Queries, Modules, Reports which we normally term as the FrontEnd. The file BackEnd will contain all the tables that you have in the database.

FrontEnd file can be distributed to as many users as you want, It will have a link to the tables thus it allows concurrent users to access the table, however not the same record at the exact same time.. BackEnd is preferablly placed in a Network location where all users have access to..

Regarding the splitting of the DB, it can be done whenever you feel. Personally I would do it towards the end i.e. before distribution of the files, as this will give only one user access over the file, thus avoiding tampering of information until final product is ready to go.

To create a FrontEnd, BackEnd file all you need to do is.. (In Access 2010) Go to Database Tools-->Under the Move Data group you will have three options of one is 'Access Database'. Click it and the magic happens..

ALWAYS MAKE A BACKUP, BEFORE YOU SPLIT. Just in case.

Hope this helps. For more info, visit...

http://www.hitechcoach.com/index.ph...base-into-application-anddata&catid=24:design

Oh thank you so much! This does help. Luckily we do not have any multi-users at the moment but eventually we will. So I don't have to worry about anyone but me getting into the DB. I just want to get this set up now so I dont' have to worry about it later. And when we do have multi-users the same file will not be accessed as each person will have their own customer to deal with. Again thanks so much.

The only thing I would add to Penguin's good description is that it is not generally recommended that any more than about 20 use the database at any one time. Lots of people can have the front end distributed but they shouldn't all be using it at the same time.

It should be noted that this figure may change depending on the complexity and the way in which the database has been designed. Also there are subtleties when dealing between LANS and WANS

Initially the best option is usually to make backups and just have a go.
IT hate when I say that but so far its served me well.

Thanks for the info. I'm with company of just 2 right now and who will be using this I believe no more than 10 over a few months to a year. So I think we are safe on the user part. ;-)

And when we do have multi-users the same file will not be accessed as each person will have their own customer to deal with

Click to expand...

I just wanted to clarify. Each user has his own copy of the FE with the forms/reports/macros/queries/code and there is only ONE copy of the BE which resides on a server share. Each of the FE's is linked to this very same copy of the BE so that the data is shared by all. Multiple people accessing the same record is not a problem. The problem is when those multiple people each try to change the same record at the same time. Access handles this very well but the messages it gives you can be confusing. It doesn't sound like this will be a problem in your application since they are very few users and extremely unlikely that they would be working on the same customer at the same time.