MS Access shared over a network

**KGComputers** · Feb 15th, 2006, 01:56 AM

Hi to all....

I have an access 2003 database which is currently running on one computer. This client of mine however wishes to add 4 computers to his business and add some personnel also. The compute numbers are C16, C17, C18, C19, and C20..I want this database to be stored on c16 only (in a shared folder)..C17-c20 will just view the database on c16. I am not using VB 6.0 for a front end...This is purely an access application..Any idea on this?

**RobDog888** · Feb 15th, 2006, 03:19 AM

All you have to do is share out the folder where the db resides. Then from the other systems you can create shortcuts to the shared folder mdb file.

**Dnereb** · Feb 15th, 2006, 03:52 AM

Or mde file.
it's better to protect your tables and query's and disallow design changes by users in a multi user enviroment.
So, ensuring all input and output is done via forms, probably will save you a lot of problems in the future.

**KGComputers** · Feb 15th, 2006, 03:55 AM

Then from the other systems you can create shortcuts to the shared folder mdb file.

Did you mean create shortcuts of access database from the shared folder? or create a shortcuts of the shared folder itself....

thanks

**RobDog888** · Feb 15th, 2006, 04:52 AM

Create shortcuts to the mdb in the shared folder. Plus, you will need Access installed on each system you wish to use it on/from.

**cbrink** · Feb 15th, 2006, 09:09 AM

The best for you will be to split the database and install the front-ends on all the machines and keeping the back-end on the server.
This will also make threading easier ensuring no data is lost.

**RobDog888** · Feb 15th, 2006, 12:23 PM

That is a solution for extending the number of users but will not guarentee any data will be lost. Access is not the best choice for multiple user database apps.

**kleinma** · Feb 15th, 2006, 05:57 PM

Originally Posted by RobDog888

That is a solution for extending the number of users but will not guarentee any data will be lost. Access is not the best choice for multiple user database apps.

agreed 1000%...

I first started programming in Access 97 (didn't get VB6 for like 2 years after that) and the thing would always crap out and have to be compacted/repaired.

I think JET in general is pretty inferior to the likes of SQL Server's little brother, MSDE.

But you work with the tools you got.. so if it has to be access, then I understand that.. just be prepaired for headaches, and compact/repair the DB nightly if possible

**RobDog888** · Feb 15th, 2006, 06:55 PM

Dont forget about making regular Backups of the db for when a Repair doesnt work.

**KGComputers** · Feb 15th, 2006, 10:07 PM

Hi....

what is the most recommended no. of users for the using the MS Access database?
I suggested to my client to extend only for three users instead of five...I have heard from my friends that access is recommended for 10 users! are they correct on this?

**RobDog888** · Feb 15th, 2006, 10:50 PM

The known limitation of Access (all versions) is 7 - 10 concurrent users. You can have more but anything in or beyond that range will result in problems.

You can extend this by splitting the db like previously posted but still will be problematic.

Thread: MS Access shared over a network

Thread Tools

Display

MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Re: MS Access shared over a network

Posting Permissions