splitting a database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am going to split a database that I have been testing in four separate
locations. I am pretty sure that all the database bugs have been worked out
in fact I have not had any problems at all. I want the database to be shared
from about 15 unique locations and that network is up and running. The
question I have is when splitting the front end and back end, can I split it
on say remote 1 (front end) to the server (back end) and map all the remotes
to the server to be say, S: drive then copy the front end of the remote 1 to
all my other remotes and have it work without much else? Am I missing
something?

Also what are the other things I need to know when 15 users are logged in
sharing the same database that may cause my database problems?

Thanks,

Dennis
 
Dennis said:
I am going to split a database that I have been testing in four separate
locations. I am pretty sure that all the database bugs have been worked out
in fact I have not had any problems at all. I want the database to be shared
from about 15 unique locations and that network is up and running. The
question I have is when splitting the front end and back end, can I split it
on say remote 1 (front end) to the server (back end) and map all the remotes
to the server to be say, S: drive then copy the front end of the remote 1 to
all my other remotes and have it work without much else? Am I missing
something?

Also what are the other things I need to know when 15 users are logged in
sharing the same database that may cause my database problems?

Thanks,

Dennis
Click to expand...

What you propose will work if you are prepared to ensure that all the client
computers have a drive S: mapped in the appropriate way. It may be
preferable to link the back end tables using a full UNC path, that way it
will not matter what mapped drives exist on the client computers.

You haven't said how remote your clients are. If they are on a LAN, then
you should be OK, but if they are on a slow WAN (say, a VPN), then this
set-up is a no-hoper: you will need to use terminal services instead.

15 users is quite a lot for Access, but without knowing anything about the
database and what the users are doing it is impossible to comment on whether
this is feasible. It might be fine, but it might be hopeless. In any case,
you need to appreciate that, due to the basic architecture of Access,
network problems or client hardware/software problems (or just plain user
stupidity) can corrupt the back-end database. Obviously the more users you
have then the greater the risk of this happening.
 
Dennis,
I have some hints that I learned the hard way.

Compile your code.

Place the FE and BE on a shared server.

After you split the database, repair and compact both FE and BE.

In the FE, goto LINKED TABLE manager and map to the backend database using
network neighborhood. Instead of s drive, it should be something like
\\pkcfp1\database\database_be.mdb

Create a MDE file from the FE database, place it on a shared server. Have
the users copy this MDE file to their individual workstations/desktop. OR
you may be able to email the MDE file to the users.

Good Luck,
David
******************************************
 
Back
Top