Disabling Link Tables and Source Location

[tps131]

I am new working with Linked tables and linked databases, I am having a few issues with this database I was given.

Issue 1.
The database is linked to a remote location with a drive letter O:\ so unless the user has a jumpdrive or partitions their drive to have an O drive available the database wont even open. Is that fixable?

Issue 2.
I am making changes to the database and need the database to be portable to other users. How can you unlink existing linked tables, instead of having the front end point to the back end I want to be able to make changes to the tables wihtout affecting the backend data.

 

[Darrylles]

Hi tps,

Firstly, you must be sure of the tables that the links refer to. Copy them / whole database(s) to the location that you wish them to reside.

In your front-end MS Access application, open it in design mode.
Tools -> Database Utilities -> Linked Table manager.
Check on all of the links in there that you wish to re-assign if ALL are to the same database.
If each link points to a table in a different database, then check each in turn.
Click OK.
Tell Access where the table is (in which database) in it's new location.
If all tables are in one database, it will re-link all tables automatically.
If you have different tables in different databases, then it will automatically find each table as you point it to each database.

Done. ;-)

Regards,

Darrylle




Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@yahoo.co.uk

 

[Darrylles]

Hi again,

Issue 2. The above also covers how to produce a 'development version': simply copy the original backend database(s) AND frontend elsewhere and work on them at will - after re-linking.

However, YOU will have to manually maintain data-integrity / synchronicity when you choose to implement your new front-end / back-end application.

i.e. you will need to ensure that you have a few hours where no users are updating the 'live' tables. Easiest way is to 'remove' their frontend application (they can't access it then).

Empty your development version tables completely (apart from tables that you may have added).
Get the 'live' table data into your development version.
Move the original frontend/backend databases to a backup.
Move your development frontend/backend databases to the 'live' locations.
Re-link the frontend links to the backend tables.

It may 'sound' complicated, but is relatively simple if you logically step-by-step through it.

Each user should then be able to use their original short-cut to your new version.

Hopr this helps.

Regards,

Darrylle












Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@yahoo.co.uk