|
|
|
|
Getting started is actually quite simple, but like most things if you have follow all the right steps. This page will walk you through the process and offer a few things that tripped the author up. OverviewThe ODBC driver and application software need to be loaded on the workstation where you will be using the connection. If you are in a client/server environment, you will need to make sure that you have access to the folders where the Eclipse data is stored. Each workstation that will be using the ODBC connection needs it's own licensed copy of the driver and must be set up seperately. Loading the ODBC DriverThe ODBC driver is written by a company called FairCom. With the driver diskettes you got from HNA, you also received the FairCom ODBC Driver End-User Guide. Loading the driver is as simple as running the SETUP.EXE program on disk 1 of the 3 disk set. Set Up the DSNIf you don't know what a DSN is, consult the FAQ. Open the ODBC Data Sources icon in your control panel. You should see a dialog box like this:
Notice the entry titled FairCom 32bit Driver, this is the sample ODBC connection that was set up when you loaded the FairCom driver. To make your DSN connection, click the "Add" button and you should see this dialog box:
Select the FairCom 32bit ODBC Driver, if it is not already selected, and click on the "Finish" button. A dialog box like this should now open:
Click on the "Options" button to see this:
You are now ready to fill in the details for your ODBC connection. HNA/MPNs documentation gives us these parameters.
Fill in the Data Source Name with any name that you want to call you ODBC connections. It is suggested that you keep it simple and one word or with no spaces. Using HNA/MPN's settings you can fill in most of the other options. In order for the FairCom driver to understand what all is included in the Eclipse database, it either needs a Script file or to use the Browse Method. At first I tried the Browse Method but I soon got annoyed when the software asked me to select the data files or to verify reuse of the selected data file. To solve this, I created a script file called HNA.DB and placed it in my C:\MPN directory. You can download a copy of my script file here, or you can easily create your own by following the instructions on page 11 and 12 of the FairCom ODBC Driver End-User Guide. To download a copy, right click on the link above and select Save Target As. Make sure that the file gets saved with an extension of "db". Some versions of Internet Explorer try to save it as a txt file. (Note: All the settings I show here are from my test platform which is a simple single workstation environment. Our production environment is a multi-user client/server environment, but the concepts remain the same.) (Note 2: Since originally writing this, I received the official script file from HNA. Click here to download VENDOR.DB from HNA.) Last but not least, modify the Data Dictionary Path to point to your MPN directory. You should now have a set up dialog that looks like this:
Click on the "OK" button and you are done. Initializing EclipseClick on Start | Run to open the Run dialog box.
Type "c:\mpn\eclipse32.exe newdoda" in the Open text box and click on "OK" This starts the process. Eclipse will open and you will get a message box as each table is initialized. Opening an ODBC ConnectionFor this part, we will assume that your ODBC connection's DSN is "hna" and that you want to access your connection through Microsoft Access. Open a new database. Select File | Get External Data | Link Tables to open the File Open Dialog box like this:
In the Files of type: drop down box, select ODBC.
You will probably have to scroll down to the last selection in the list. Once selected it will open a Select Data Source dialog. You should see your the DSN of your ODBC Connection that we set up before. In our example it's hna.dsn. Select hna.dsn and click on "OK".
Next will open a dialog to select the Linked tables. Click on "Select All" and then "OK".
As Access loads the tables it check for unique index fields in each table. It will ask you to selected these fields for the "Appointment" table. Looking in our Database Schema document, we see that we should highlight PatientID, Data and Time. Do so and then click on "OK"
You may get errors indicating that the Jet Database Engine could not find the tables "Appointment Archive" and "Bill Archive". Click the "OK" button to continue. If you have not yet used the archive function in Eclipse V8, then these table do no yet exist. You will also be asked to select a identifier in the "Submitter1" and "Userlog1" table. Click "OK" to each of these dialogs to continue the connection. You now see your database window showing your new ODBC linked tables.
Remember to be careful, the table you see here in Access are your real Eclipse data. Any changes, deletions, etc will have direct impact on your real data! |
|
Send mail to feedback@huntfamily.com with
questions or comments about this web site.
|