INTRODUCTION

GShell, GQueryBrowser, GQuery, GQ_ADO_XtraTables, Documentor, and GBDSTools are application interfaces designed to work with databases built according to the GlobalDB schema. The applications and the databases communicate using middleware, service software that lies between the programs and the databases. At this time, the databases are managed by the Microsoft Jet Engine (which lies beneath MS-Access). The programs use the Microsoft Data Access Components (MDAC version 2.1 or later); communication between MDAC and the MS-Jet Engine is done with an OLE DB provider. This method is required with MS-Access 2000 and up, and may be used on computers having the proper ADO components installed (see Requirements). If that middleware is not installed and configured properly, the programs will not work.

The GlobalDBSystem utilities do not "know" about MS-Access, or even where the databases are located and what their file names are. Each database is known to the application programs by its "alias", which is defined using the Data Link Properties software tool. Once these aliases are defined, the middleware activity happens in the background and can be ignored.

DEFINING THE ADO ALIAS STEP BY STEP

1. Using Windows Explorer, browse to the location on your computer network where you have copied the folders GlobalDBSchema321 and Data 321 of this open file. Enter the folder GlobalDBSystem321 where the application interfaces will reside if they have not been moved. If the applications have been moved elsewhere, navigate to the folder where they now reside.

2. From the menu bar, choose File / New / Microsoft Data Link. This creates a new file with extension UDL. If "Microsoft Data Link" is missing from the menu, the following extra steps will rectify the situation:

   • First, you must make sure that file extensions are always visible. This can be done by clicking on the menu bar and finding "Options" (the menu is slightly different in each version of MS-Windows).

   • On the View tab page of the Options dialog box, there is an option labeled "Hide file extensions for known file types"; this check box should be un-checked. Then click Apply, then OK to close the box.

   • From the menu bar, choose File / New / Text Document; this creates a new file called "New Text Document.txt".

   • Rename the prefix of this file to identify the database you wish to use. The name MUST start with "Global" (upper case "G", lower case "lobal"). Change the extension of the file from .txt to .udl (the extension is not case sensitive). For example, a example database alias file could be called "Global_Example.UDL" or "Global_example.udl".

   • A window will show up with a warning message about changing the file type; click OK to confirm the change. You can now proceed with Step 3.

3. Rename the prefix of this file to identify the database you wish to use. The name MUST start with "Global" (upper case "G", lower case "lobal"), and retain the extension UDL. For example, a example database alias file could be called "Global_Example.UDL" or "Global_example.udl".

4. Once the name has been changed, double-click on it to execute the configuration program. A window appears (titled "Data Link Properties").

5. Open the "Provider" tab and select "Microsoft Jet x.xx OLE DB Provider" (x.xx could be 3.61 or 4.0; choose the highest number).

6. Open the "Connection" tab. Under the first choice, browse until you find the database you are presently configuring (for example, "sample.mdb"). Leave the Username as Admin and leave Blank password checked. Click on the "Test Connection" button to make sure everything works fine and click OK to acknowledge.

7. Click OK to close the "Data Link Properties" windows. This completes the operation.

GlobalDB System Site Map | Presentation | Requirements | Software and Scripts | Aliases | Using GShell | Using GQuery | Using Documentor

---

Important notices and disclaimers

2014-09-26