Using an MDB Over A Network

[PhoenixBB]

I have an MSD that I want to be sat on a server. There are a couple of laptops that are linked into the network.

My question is can this MSD be accessed over the network and what problems will this cause if for argument sake it is being accessed at the same time by more than 1 user or if data is being added at the same time by more than 1 user.. ? ?

Many thanks in advance ..

 

[Minkers]

With more than one user you really should split the database into frontend/backend. This way your tables and data are not accesible to the user, as well as they are protected should something happen. There are really no problems with multiple users in a database, however it will only allow one user to edit a record at a time.

 

[PhoenixBB]

Thanks for a quick response.

I am new to Access.

When you say:

"it will only allow one user to edit a record at a time"

Am i right in translating that to mean that if the DB has 15 records then theoretically 15 people can be in the DB edditting each of these records as long as 2 people are not edditing the same record.

Also will it report that the record is being edditted elsewhere??

 

[Minkers]

What the user will get when trying to edit a record that has already been opened by another user is a "Record locked" error. When the other user has completed the changes and saved the record they are working on, the record becomes unlocked.

 

[PhoenixBB]

Thanks again Minkers, final question is what do you mean by splitting it into frontend and backend and what are the advantages of this??

Thx in advance

 

[Minkers]

When you split the database into frontend/backend it means that you have the tables in one database, and the forms, queries, reports, and whatever else in another database. Often the frontend part is an MDE file so the user cannot gain access to the coding to change it. (Make sure you keep a backup copy so you can make changes if you do this though!) In this way it is better for the data because there is less chance of corruption. Also, should something happen to one of the front ends, you can easily replace it instead of having to take time figuring out the problem. Changes can also be made without very little inconvience to your users, and upgrades to the front end only require giving the users the new file.

It is a more sensible way to protect your data, and if you don't want to hand out multiple copies of the front end users can still use the same front end over the network. With no access to your actual tables, the chance of data corruption goes way down. If you do decide to do this, it should be the last step before releasing your database. Backup your database, and use the tools provided by Microsoft to make it easy for you.

HTH
Minkers

 

[PhoenixBB]

Thankyou very much Minkers for breaking this down into a way I fully understand. It is very frustrating trying to decrypt something you don`t understand but I guess everyone was a NoOb at some point

Thx

 

[AccessDevJunior]

Using an ms access as a back_end will only support up to 40 users, if you have more users on the network it may be best considering moving towards using a sql serverback_end.

 

[PhoenixBB]

There are only 4 computers on the network so I think it will be okay according to my research but thx for the input..