Odbc Data Source Administrator 64-bit Download
Debora Mccaffery
The SQLDataSources function returns all versions of user DSNs, regardless of the architecture of the application. The SQLDataSources function that is called in a 32-bit application returns only system DSNs for 32-bit drivers but returns user DSNs for both 32-bit drivers and 64-bit drivers. Similarly, the SQLDataSources function that is called in a 64-bit application returns only system DSNs for 64-bit drivers but returns user DSNs for both 32-bit drivers and 64-bit drivers. Therefore, if the application makes a connection by using a user DSN that is returned from the SQLDataSources function, you may receive the following error message:
For example, consider the following scenario. You create a user DSN for the 32-bit driver 'Microsoft Access Driver (*.mdb)'. This driver doesn't have a corresponding 64-bit version. The SQLDataSources function that is called in a 64-bit application returns this 32-bit user DSN. However, if you make a connection through this 32-bit user DSN, you receive the error message that is mentioned earlier in this section.
To work around this problem, use the appropriate version of the ODBC Administrator tool. If you build and then run an application as a 32-bit application on a 64-bit operating system, you need to use the %windir%\SysWOW64\odbcad32.exe ODBC Administrator tool to create the ODBC data source. To indicate the type of DSN, you can add '_32' to the 32-bit user DSNs and '_64' to the 64-bit user DSNs.
The 64-bit ODBC Administrator tool can be invoked from Control Panel to manage user DSNs and system DSNs that are used by 64-bit processes. On a 64-bit operating system, the 32-bit ODBC Administrator tool is used for Windows on Windows 64 (WOW64) processes. You must directly invoke the 32-bit ODBC Administrator tool from the SysWoW64 folder. You can use the 32-bit ODBC Administrator tool to manage user DSNs and system DSNs that are used by WOW64 processes.
Registry redirection is enabled for this registry subkey. Therefore, system DSNs for 32-bit drivers and for 64-bit drivers are separated. The 64-bit ODBC Administrator tool doesn't display system DSNs that are created by the 32-bit ODBC Administrator tool. Similarly, the 32-bit ODBC Administrator tool doesn't display system DSNs that are created by the 64-bit ODBC Administrator tool. Also, the 64-bit ODBC Administrator tool doesn't display system DSNs that use 32-bit drivers. Similarly, the 32-bit ODBC Administrator tool doesn't display system DSNs that use 64-bit drivers.
The Microsoft ODBC Data Source Administrator manages database drivers and data sources. This application is located in the Windows Control Panel under Administrative Tools. Beginning in Windows 8, the icon is named ODBC Data Sources, and on 64-bit operating systems there is a 32-bit and 64-bit version.
In 64-bit Windows, there are two ODBC Data Source Administrators: a 32-bit and a 64-bit version.
The ODBC Data Source Administrator that is accessible in the Control Panel, under Administrative Tools, is the same bitness of Windows.
To create or modify the 64-bit ODBC Data Source on Windows 64-bit, access the ODBC Data Source Administrator directly from the Start menu or Control Panel.
To create or modify the 32-bit ODBC Data Sources on 64-bit Windows, run the 32-bit ODBC Data Source Administrator from C:\WINDOWS\SysWOW64\odbcad32.exe.
In a single process, all of the code must be either 32-bit or 64-bit.
Data Source Names (DSN) are likewise separated by bitness since a DSN is defined for a specific driver.
Hence, Datacom Server provides both a 32-bit ODBC driver and a 64-bit ODBC driver.
"...Use the Microsoft ODBC Administrator to configure access to Datacom/DB. You must have Administrator access rights to create or modify any ODBC data source, including the default ODBC data source for Datacom. If you do not have Administrator access rights, the data source can be viewed as read-only....
To configure access to Datacom/DB
Open the Data Sources (ODBC) applet under Control Panel/Administrator Tools.
The ODBC Data Source Administrator window appears showing the User DSN tab. Click the System DSN tab... ..."
We'd need to know how it's "Failing". Any error messages? I have never had a problem in Quick Fields as long as you go through the ODBC setup/wizard from within Quick Fields and not through Control Panel.
Workflow can be either 32-bit or 64-bit on a 64-bit OS, the installation defaults to x64. The Office ODBC drivers need to match the CPU-architecture for Workflow. If you decide to use 32-bit Workflow, installing Office will give you 32-bit drivers for Access. If you go with x64, then you will need to install Microsoft Access Database Engine 2010 in order to get x64 Office drivers.
In all cases, I would recommend going to the Windows ODBC Data Source Administrator through QF or WF. They will launch the correct version needed by the software. Launching the ODBC Data Source Administrator through Control Panel on a 64-bit OS will give you 64-bit version. If you want the 32-bit version, you can launch it from C:\Windows\SysWOW64\odbcad32.exe.
Sticking to just the Excel one, so you can make it through the ODBC wizard then? Picking the appropriate driver, making it a system or user dsn, and get past authentication? Can you pick the sheet or is that when you get the error? Or do you get the error in the output pane when you try and scan? Also how about your Test Query button after it is set if you can get that far?
I don't think that is going to be the driver. What is the format of your excel sheet? I have had this a few times and it ends up being that the columns need to be formatted as numbers, dates, text, etc. Have you tried changing the format of the columns or at least the one you are doing the lookup off of?
Same as above, there is not enough information to troubleshoot. What software are you using? Where are you seeing the error? What data are you passing in? Are you reading from or writing to the Excel file? Excel internally set the column types based on the data present, so the error is most likely indicating an issue with the actual value.
I have an excel spreadsheet (I've tried it with both a 97 version and a 2015 excel version) that has the data set up. I have a field called Image Name. I have set up the Quick Fields session to pull the data for the fields when the data in the Image Name field equals the actual image name. I.E. I have an image named "1" and the Image Name field has a "1" in it. I have set it up to pick up the other fields in the spreadsheet to populate the template fields. When I run the Quick Fields session I am getting this error:
I have tried changing the data type to every data type possible and I am having no luck. My biggest frustration is that this is the exact same set-up that I have used in Quick Fields 7 and it works fine.
There is no Office 2015, I expect you meant 2013. The column type set in the user interface has no impact on the ODBC driver. The driver decides the column type by sampling the first few rows. Anything that does not match that data type is ignored. I can't confirm it without looking at the spreadsheet, but I expect Excel thinks the column is a string rather than a number column.
A data source is a source of data combined with the connection information that is required to access that data. Examples of data sources are SQL Server, Oracle RDBMS, a spreadsheet, and a text file. Examples of connection information include server location, database name, logon ID, password, and various ODBC driver options that describe how to connect to the data source. This information can be obtained from the administrator of the database to which you want to connect.
In the ODBC architecture, an application such as Access connects to the ODBC Driver Manager, which in turn uses a specific ODBC driver (for example, Microsoft SQL ODBC driver) to connect to a data source. In Access, you use ODBC data sources to connect to data sources external to Access that do not have built-in drivers.
Define a data source name (DSN) by using either the ODBC Data Source Administrator to store the connection information in the Microsoft Windows registry or a DSN file, or a connect string in Visual Basic code to pass the connection information directly to the ODBC Driver Manager.
File data sources (also called DSN files) store connection information in a text file, not the Windows registry, and are generally more flexible to use than machine data sources. For example you can copy a file data source to any computer that has the correct ODBC driver so that your application can rely on consistent and accurate connection information to all the computers it uses. Or you can place the file data source on a single server, share it between many computers on the network, and easily maintain the connection information in one location.
A file data source can also be unshareable. An unshareable file data source is contained on a single computer and points to a machine data source. You can use unshareable file data sources to access existing machine data sources from file data sources.
In a module, you can define a formatted connect string that specifies connection information. A connect string passes the connection information directly to the ODBC Driver Manager, and it helps simplify your application by removing the requirement that a system administrator or user first create a DSN before you use the database.
I'm trying to create a DSN to use accessing MySQL from powershell.When I open up %windir%\system32\odbcad32.exe (the default 64-bit ODBC Administrator) and click on the system DSN tab, it gives the warning
"You are logged in with a non-administrative privileges. System DSNs could not be created or modified"I am the sole administrator on the system and am logged in as administrator when this happens. I have also tried starting the ODBC Administrator by right-click run as administrator, same result.
@olimpio
Your go-to resources on how to connect to databases is this list of Data Sources and the help for Input Data tool. Many of the Data Sources have articles in Community, and Hadoop is no exception. If you're new to Alteryx this article on how to search Community might be helpful to you.