Linked Table Management Guide V1.00

$12.95

This guide is designed for Microsoft Access database developers of split databases - one file, the back-end, containing nothing but data tables, another file, the front-end, containing all interface objects such as forms, reports etc, and linked tables to the back-end.

In this system the front-end 'links' to the data tables in the back-end. The front-end contains no volatile data. All data is accessed via linked tables. This is the preferred method of database development and has many advantages and few disadvantages.

We assume you have already made the decision to develop a split database in Microsoft Access, and understand the advantages, but have come across the one main disadvantage.

That disadvantage is that if the back-end database is moved or the location on a workstation is remapped in another way, the front-end linked tables fail to work, as the link information still contains the old path to the data file. To make it worse, you don't know there is a problem until something actually tries to access the data.

This link information can be refreshed manually, but this is time consuming and where there are many workstations linking to the same data file, tedious in having to go to each workstation and repeat the procedure.

There are many ways to fix this problem, and this guide provides an excellent solution.

The solution is to provide code that when executed on loading the first form, checks all links and if necessary requests from the user the new path to the database. Once provided the path is stored, in an 'INI' file, then on subsequent startups it is used to verify the location of the data file.

The guide provides clear explanations and ready to use functions and code to include in your own database. You can use this code for your own use in as many databases as you wish.

	The VBA code is clearly commented and formatted for easy reading and customisation if necessary.
	Instructions for using all VBA code and implementing the solution are presented in a simple step-by-step format, well commented and illustrated where necessary.

	All complex Microsoft Access dialogs encountered in implementing the solution are identified, illustrated and discussed.
	A concise glossary of all common terms provides clear explanation and, where necessary, are illustrated for clarity.

Suitable Uses

Split Database Systems

If the Microsoft Access database you are developing is intended for multiple users, then a split database is the recommended option. In fact, we recommend split systems for all database.

Features

• A complete ready-to-use VBA function for managing links in your Access databases.
• VBA code is commented and correctly formatted for easy reading.
• Full explanation of all VBA code.
• Easy step-by-step instructions for implementing the solution.
• Screenshots and explanations for all dialogs encountered.
• Glossary of common terms.

$12.95