Search This Blog

2009-05-13

Test Any OLE DB Provider in Windows (32-bit and 64-bit)

Windows recognize file extension .udl (64-bit) and .udl32 (32-bit) which are OLE DB configuration file.

By creating an empty .udl or .udl32 file, we can bring out OLE DB configuration screen to test both 32-bit and 64-bit OLE DB.

Most users are clueless how to test out OLE DB once it is installed by Oracle, IBM DB2, or SAP. This is the procedure

32-bit OLE DB Test

Procedure A: Configure Windows 64-bit to recognize .udl32 extension. Not require for 32-bit Windows

1. Create a new association for file type UDL32 that will execute the 32-bit version of rundll32.exe
1.1. Launch the Windows Explorer
1.2. Choose Tools->Folder Options -> File Types Tab from the Menu
1.3. Click New Command button to add a new extension
1.4. Enter UDL32 in the text box
1.5. Click on the Advanced command button
1.6. Optional. Click on Change Icon button to choose the appropriate icon for the extension
- Note, the Standard Data Link Properties icon is located at: C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
1.7. Click New button to add a new action
1.8. Type 'open' in the action text box
1.9. For "Application used to perform the action". Enter C:\WINDOWS\SysWOW64\Rundll32.exe "C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll",OpenDSLFile %1
- Note: Replace Windows directory accordingly
1.10. Close everything


Procedure B: Testing 32-bit OLE DB Provider
1. Create an empty file on any drive and directory
2. Rename the text file to testoledb.udl32 (the icon for the file should change at this point to a computer in front of a spreadsheet)
3. Double click testoledb.udl32. A Windows connection dialog box will appear, with Connection tab visible
4. Click the Provider tab, select OLEDB provider to test (Ie, Oracle Provider for OLE DB, IBM DB2 Provider for OLE DB)
- Note: ODBC connections can also be tested by selecting Microsoft OLEDB Provider for ODBC Drivers
5. Click the Connection tab. Enter a valid connect string for Data Source, which is TNS for Oracle. Enter a valid user and password for the database. TNS needs to be configured in tnsnames.ora (Oracle)
6. Click the Test Connection button to ensure it is successful

64-bit OLE DB Test
This step is applicable to 32-bit Windows to test 32-bit OLE DB

1. Create an empty file on any drive and directory
2. Rename the text file to testoledb.udl (the icon for the file should change at this point to a computer in front of a spreadsheet)
3. Double click testoledb.udl. A Windows connection dialog box will appear, with Connection tab visible
4. Click the Provider Tab, select OLEDB provider you're trying to test (Ie, Oracle Provider for OLE DB)
- Note: ODBC connections can also be tested by selecting Microsoft OLEDB Provider for ODBC Drivers
5. Click the Connection tab. Enter a valid connect string for Data Source, which is TNS for Oracle. Enter a valid user and password for the database. TNS needs to be configured in tnsnames.ora (Oracle)
6. Click the Test Connection button to ensure it is successful

Note: If OLE DB Provider is installed, and yet doesn't show up in either test, then it is possible regsvr32.exe is replaced by some software, and can't register DLL properly. Look for this file from other PC, and replace it. Remember to take a backup

No comments:

Blog Archive