Banner ODBC Driver (Oracle 11g)

Transcription

1 Banner ODBC Driver (Oracle 11g) Converting An Existing Access Database To Use The New ODBC Driver Latest update (by Paul M Baxter): 05 Mar 2010 This document explains how to convert the Banner ODBC links in a Microsoft Access database after installing the new (11g) ODBC driver. The data source names (DSNs) generated by this driver are not interchangeable with the previous version. So, to avoid confusion, the new PRODuction DSN is called BANNER_ODBC_PROD. (It was previously called SIMS_ODBC_PROD or SIMS_ODBC ). This means that the new driver requires MS Access users to change their existing ODBC links so they do not try to use the old driver, which will have been uninstalled. Until you do this, you will not be able to run any previously created ODBC queries. However, this is quite simple to do and uses the Linked Table Manager within Access, which conveniently avoids having to re-create all the existing links to views and tables. Option A Learn How To Convert Your Tables From A Demo There is a short demo that describes the process, which can be started from HERE. Option B Convert Your Tables By Following These Steps This example uses Access 2007, but the same principal applies to all versions of Access: [1] Open the database to be converted and select the Database Tools ribbon, then click on Linked Table Manager. (Alternatively, you can right-click on any linked table and select Linked Table Manager from the pop-up menu).

2 [2] This will open the manager, which will contain a list of all linked tables with their current parent DSN shown next to it (in brackets). In this example, all tables are connecting to Banner via the old SIMS_ODBC DSN: [3] Tick each table that you wish to re-connect to the new driver s DSN. This will typically be all of them, in which case click on Select All :

3 Then click on OK [4] Select Machine Data Source in Data Source window that appears: Then select BANNER_ODBC_PROD and click OK NOTE: Sometimes, the DSN selection window might not appear at this point, and the Linked Table Manager may skip directly to step 7 instead.

4 If this does happen, resume from step 3 and tick the Always prompt for new location box before clicking OK again. This will then force the DSN selection list to appear. [5] Enter your Banner username and password in the Driver Connect dialogue (leaving the Service Name as it is), and the click OK : [6] NOTE: If your list of tables to be converted (i.e. the ticked ones) contains even just one table with a different DSN to the others, then you will be asked to log-on (i.e. steps 4 & 5) for each table in your list. For example, you may have 10 tables using DSN SIMS_ODBC and 4 using SIMS_ODBC_PROD, so you will need to log on 14 times! Therefore, if you do have ODBC table-links using SIMS_ODBC and SIMS_ODBC_PROD, it will be quicker to select all of one type first and then the other one separately. This means you will be asked to log on just once for each type (i.e. twice!). [7] There will be a delay while the tables are converted to the new driver s DSN, and then you should see a success message: Click OK

5 [8] The Linked Table Manager should reappear with the list of tables again. But this time, the tables should be attached to the new BANNER_ODBC_PROD DSN: Click Close to complete the process. Your database links should now work again, but connecting to Banner via the new 11g driver. Option C Convert Your Tables Manually (DIY) In some isolated cases, the Linked Table Manager may not work, and you may receive an ODBC error message when trying to run it. (An understanding of this problem and its solution are both still pending). The work-around in these cases is to individually delete each ODBC link to a Banner table or view, and then to recreate it using the new driver, ensuring that the names are identical. (For example, do not replace PUBLIC_SWCSTUD with BANINST1_SWCSTUD by selecting it from the wrong place in the list of tables). If you do encounter this problem (or any others) and need more assistance, please contact the SIMS Team via the ISS Helpdesk.