Fixing problems with a front end - problems!

Sharky II

Registered User.
Local time
Today, 01:22
Joined
Aug 21, 2003
Messages
354
Hi guys

A while back i made a pretty complicated database for a travel agency. I then split it and stored teh backend on the server at their office, and a copy of the front end (forms and queries) on each users machine. This worked fine.

The problem is that there are some (quite a few) problems with the front end i need to change. I took a copy of both the current front end and the latest back end.

How can i view the front end again, as they're split (and obvious the back end is in a different place on my drive to where it was on the office server)? Do i have to go to the back end and then import all the forms and quieries?

Also, does anyone have any tips on deployment? They have some 2000 records in the backend, that i don't want to delete! How can i then re-insert the front end back on each machine, after i've made the changes - ie it has to have the right pointer to the back end etc.

Is there some sort of merge feature that would work, and then i should replit it just like i did last time? They are currently using the database (while i fix the front end on my machine) and i want to 'slot in' the new front end. If i split it etc again, then i'll end up with problems in overwriting the back end - no?

Sorry if these are dumb questions, i've not been into access stuff since last xmas!

Many thanks guys

Eddie
 
Last edited:
You need to relink your copied front end to your copied back end. From the menu bar click... Tools / Add-ins / Linked Table Manager. I suggest that you leave the back end alone unless you have to make a design change to it. Fix your copied front end, replace it over the users current front end, relink the tables, then give that copy to the other users.

Good luck!
 
Thanks for your help!

I'll try that at work tomorrow and let you know how it goes!

Cheers

Edd
 

Users who are viewing this thread

Back
Top Bottom