Getting Copy of modified Split database to several regions

  • Thread starter Thread starter Pamela via AccessMonster.com
  • Start date Start date
P

Pamela via AccessMonster.com

Hi All;

I have been given a very complex database which is split. The front end
(Audit) also includes some tables (ie, Employee table with employee names) &
the forms I modified, while the backend (Data) contains several tables worth
of data, 3 of which I had to modify which contain "weights" for quality
review audits, for example, error #1 takes off 3 points, error #2 takes off .
5 points, etc.

Several different regions have a copy of the same Database, with all
databases containing different data, but we want to give them a blank copy of
the one I have modified, inclucing the modifed tables on the backend. What
would be the best way to accomplish giving others a copy of this database
across a network? Sorry for my ignorance, but I have never done this before.
I'm just wondering about relinking tables, etc.

Thanks
 
When you say "giving others a copy of this database across a network", I
hope you mean you're planning on copying the back-end database to the remote
locations. Access does not work well over WANs.

Also, hopefully you're not sharing the front-end: each user should have
his/her own copy of the front-end, preferably on their hard drive. You might
want to take a look at the free Auto FE updater Tony Toews has at
http://www.granite.ab.ca/access/autofe.htm You may want to reconsider having
tables in the front-end unless you've included a way to update those tables.

Add code to your front-end to relink the back-end. There's sample code to do
this at http://www.mvps.org/access/tables/tbl0009.htm at "The Access Web"
 
Yes on "copying the back-end database to the remote
locations."

Each region will have a copy of the frontend sitting on their shared drive
which they have access to, but I will only have access to the server
temporarily to place it there. They will then place a copy of the frontend
to their local drives like we currently do.

The tables that are in the frontend contain static data (ie, the employee
names which can be modified via the application) & the table containing
weights which I mistakenly said were on the backend. The weights will be the
same throughout the regions, and I was thinking I could give them
instructions on how to add employees once they get the front end back. Is it
OK to keep these tables on the front end since the data is for the most part
static (basically they are look-up tables)?

The backend contains the audit data which is constantly being changed on a
daily basis.

The application has linking built into it, it is actually a very well-
written/designed application, and I have used it to relink the tables in the
past. I guess I'll have to supply instructions for that as well.
 
You really shouldn't have multiple users sharing the same front-end. That
significantly increases the risk of database corruption.
 
The regions will each get a copy of their respective front-end. I'll make
sure they know to place a copy of the region's front-end onto their hard
drives.

Thanks for the links & the help!
You really shouldn't have multiple users sharing the same front-end. That
significantly increases the risk of database corruption.
Yes on "copying the back-end database to the remote
locations."
Click to expand...
[quoted text clipped - 36 lines]
Click to expand...
 
Back
Top