Microsoft ODBC Driver for Oracle Datasources. Good Day,Im abit confused as to why im having this problem. I recently installed Oracle1. R26. 4bitversion1. Windows 7 Ultimate OS. Bit Oracle Odbc Driver On 64 Bit Windows' title='32 Bit Oracle Odbc Driver On 64 Bit Windows' />Now tried to connect MS Access 0. Oracle Database by doing the following a. In access i clicked External Data Tab More ODBC Databases Link to data. Now when the data source box comes up I click Machine Data Source New System Data Source Next Choose MS ODBC driver for Oracle Next Finish. When i do this i get the following error The Oracletm client and network components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7. You will be unable to use this driver until these components have been installed. Now i launched the Microsoft ODBC Administrator and did the following b. Progress DataDirect for ODBC for Oracle Wire Protocol Driver Version 8. Clicked the System DSN Tab Add now i see the new installation name and version. I select the new name Oracle in Ora. Db. 11ghome. 1 and click finishb. Now on the ODBC Driver Configuration i enter Datasource name, Description, TNS Service Name and user. ID,  scott then i hit the test connection button. Enter the password, Bingo Test SuccessfulNow when i go back to access 0. Select Data Source box comes up and click on the machine Data source tab now in here i dont see the new machine data source i just created, shouldnt the datasourse be in hereThe following, taken from here, was not mentioned here If the Oracle Client is 32 bit, it will contain a lib folder but if it is a 64 bit Oracle Client it will. Create an Oracle DSN using the iAnywhere Solutions 12 Oracle ODBC ODBC Driver. Make sure that your Oracle client configuration file tnsnames. During the install of an application on a 64bit Windows machine, the application was unable to list the ODBC System DSN because it had been setup as a 64bit DSN and. However i was able to create a user data source but when i try to use that to connect to oracle using access. Install Program Using Logon Script Group. ODBC call failed. MicrosoftODBC Driver Manager The specified DSN contains an architecture mismatch between the Driver and Aplication 0Now everything else works Sqlplus connects fine, Sql developer connects just fine, its just that ms access 0. Installing AQT on a 6. Windows. By default, AQT is installed as a 3. When you install AQT on a 6. AQT will also be installed you will have icons on your desktop for both the 3. AQT. the 3. 2 bit version of AQT can run on both a 3. Windowsthe 6. 4 bit version of AQT can only run on a 6. Windows. On a Windows 6. AQT. Which one you will use will depend on the the ODBC Datasource you are wishing to connect to The 3. AQT can only connect to a datasource which uses a 3. ODBC Driver. The 6. AQT can only connect to a datasource which uses a 6. ODBC Driver AQT v. AQT v. 8 and earlier versions of AQT run OK on a 6. Windows. These versions of AQT are 3. ODBC Driver. AQT 3. AQT 6. 4 bit. The 3. AQT executables are the same program and have identical capabilities they have just been compiled with different settings. Their performance is almost identical, though the 3. The 6. 4 bit executable uses more memory than the 3. This is because all memory address pointers use 6. The only advantage of the 6. AQT is that it can use more memory. GB of memory. In most cases AQT uses far less memory than this. However if you have a lot of physical memory on your machine, and you wish to display very large tables, the 2. GB memory limit of the 3. AQT may be a limitation for you. In this case, running the 6. AQT will allow you to display a larger amount of data. ODBC Drivers and Datasources. On the Signon window you will be shown a list of datasources. On a 6. 4 bit machine this can be confusing, as this list can contain some datasources you will be unable to connect to. In addition some of your ODBC Datasources may not appear in this list. This list contains System Datasources which are appropriate for the version of AQT you are running. In other words, if you are running the 6. AQT you will only see the 6. System Datasources, if you are running the 3. AQT you will only see the 3. System Datasources. User Datasources both 3. AQT you are running. You may not be able to connect to all the User Datasources as some of these may be incompatible with the version of AQT you are running. Note that you cannot tell from this list which are System and which are User Datasources, nor can you tell which are 3. If you attempt to connect to connect to a datasource that uses an incompatible ODBC driver, you will get the message Data source name not found and no default driver specifiedor. The specified DSN contains an architectural mismatch between the Driver and Application. The solution is to connect to this datasource using the appropriate version of AQT 3. This is described in more detail in http support. Adding and Managing Datasources. You can add new datasources with the New button or ODBC Admin Add. In both these cases you will only see the Drivers which are appropriate for that architecture of Windows. In other words, adding datasources in this way works well. Configuring existing datasources runs into the same problem as mentioned in the previous section. The list of datasources may contain datasources which are not valid for that version of Windows. Clicking on Configure or ODBC Admin Configure can give you the message The setup routines for xxxx ODBC Driver cannot be found. The solution here is to use the appropriate version of AQT for that datasource. Oracle Problem. When you attempt to connect to an Oracle database, you may get the message TNS could not resolve the connect identifier. There are a number of possible causes of this error message see Oracle Diagnosing Connection Problems. However, there is a problem in the 6. Windows environment that may be responsible for this problem. This is discussed below. By default, AQT will be installed into C Program Files x. Advanced Query Tool. The Program Files x. However there is a bug in the Oracle client when you run a program which has a bracket in the path, the Oracle client will fail to parse tnsnames. The resolution to this problem is to install AQT into a directory that doesnt have a bracket in the name. This problem has been fixed in recent versions of the Oracle Client.