Share a database over network for multiusers

[mkphan]

I have an Access 2000 database. It will be used by many users concurrently on the network. The database will be updated, data will be inserted into table, reports will be generated, queries will be performed, etc.

Would someone has the experience in this area help me out? I'm new to this area... What do I need to have and to do?

Thanks in advance for your help,
MK

 

[OverDrive]

Do you have access to an SQL server? Or will this be located on a mutual networked drive?

If it is on a mutual drive, try doing the Database splitter wizard, it splits the database and links tables, queries, etc... so that all users have the ability to share the same database without incurring the size of the database.

If you are running this on an SQL server, better ask someone else . . . but I think Database Splitter Wizard (imo) is your best choice . . .

lemme know how it goes ok!

Chance~

 

[Francescina]

You need to split your application it two files:

1.) Frontend with all datbase objects except tables
2.) Backend with only the tables

Place your backend file on the server and link all tables into your frontend file.

Install this frontend file on the clients.

ATTENTION: the drive with the backend needs to have the same drive letter on all clients!!

The clients need READ/WRITE and DELETE (very important!) rights on the server directory.

Furthermore, you need an error trapping procedure (lock errors), your application's queries and table structure (indexes, normalization) needs to be optimized and a automatic backup of the backend is veryveryveryvery important (risk of damaged backend if clients are not disciplined).
Think also of securizing the frontends (MDE format is an advatage) and if your backend data needs protection be aware that the tables can no longer be linked into the frontends.
There are a couple of other important details that I do not have the time to write down, I strongly recommend the "Network"-section of the ACCESS ONLINE ENCYCLOPEDIA (

http://www.unsoftwareag.com)

for details.

Fran

 

[DbaseInc]

It will be very important to break the database up. If you have SQL server it would be much better, but if not you can use Access 2000. Realize that there is a problem with concurrent users in microsoft access. Currently a database with over 14/15 users will cause problems. If you split the data into MDB with data(Tables), and then put applications out on the server. Another method is to develop the access database with linked tables or SQL Calls. Finish the database and make it an executable or MDE that you distribute to the users. This will prevent the problem.

 

[tlbroadbent]

I recommend splitting the database also. When linking backend data tables to the frontend use the UNC rather than a drive letter. That avoids a lot of connection problems. Terry

http://members.home.net/tlbroadbent/index.htm

 

[Rhonin]

All of the previous listed suggestions are more than valid. A Front/Data split is essential. One problem I have run into (under Novell) was I had to maintain a workstation with the data table open as a remote server otherwise novell would lose the lock link (.ldb file) automatically making the data exclusive use only. This problem did not exist if run under other server software.

 

[Guest_imported]

how to make an executable file for microsoft access database