Database Search
TechHome
 |
- !!NEWSFLASH!!
- 1437 or 3437 Extender Load Error
- 3132 error when using DAO
- 521 Attribute string too long
- Access SQL Update
- An SQL Tutorial
- Automated ODBC Data Source creation
- Calling a MS SQL Server 2000 Stored Procedure
- Change database then Update then count rows
- Compact an Access Database
- COMPACT_DB and Password MDB Files
- Continue a SQL Query after a Warning Message from Driver
- Create a System DSN for a TXT File Problem
- Create an SQL DSN with User name and Password
- DSN Connection Strings
- Execute an Oracle stored procedure
- Explanation of ODBC Usage
- Get Installed Driver Information
- Get Parameters from a Stored Procedure
- How Does qBindCol Work
- How to Do a Simple Sql Query
- Invalid Cursor State Error
- MDAC Invalid Object
- Microsoft SQL Server ODBC driver Info
- More on How ODBC Works
- ODBC and Services
- ODBC and SQL
- ODBC DSN Maker
- ODBC DSN Port Configuration
- ODBC Extender with WebBatch problems
- ODBC on 64 bit System
- ODBC SQLDescribeCol Example
- ODBC WHERE Syntax Blank Data
- Pervasive SQL Syntax Error
- Problem Adding System DSN for SQL Server
- Problem Using qConfigData with the Oracle ODBC Driver
- qConnect Crashes with Exit Code -1073741571
- qExecDirect and SQL Questions
- QExecDirect Second handle issue with SQL Server Drivers
- qFetch with Empty Cell
- qFetch with qBindCol and qGetData
- qGetData 50 columns limit
- qLastCode to Check these SQL Return Codes
- Read Information from Lotus Notes
- Retrieving data after a SQL JOIN
- Return Codes in ODBC Extender
- s0022 error from SQL Server Driver
- Specify SQL Server Password in qConfigData
- SQL Server SELECT SUM Statement
- SQL SUCCESS WITH INFO
- Syntax for Insert Into Access
- Updating ODBC.INI File over the Network
- Using WildCards in an ODBC SQL Statement
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
ODBC on 64 bit System
Keywords: ODBC on x32 x64 64 32 bit platform system ODBC32 odbcconf.exe
Note: WinBatch and the ODBC extender now both have 64-bit versions.
WinBatch is a 32 bit application. The current version of WinBatch has been thoroughly tested on 64 bit platforms. However, Because the ODBC Extender is compiled as a 32 bit DLL, it acts as a 32 bit App. All of the ODBC operations are treated as 32 bit operations on 64 bit platform.
The ODBC Extender would have to be compiled as a 64 bit Dll in order to handle 64 bit DSNs. That is not likely to happen any time soon.
It's important to understand which kind of DSN you have. On an 64 bit system, you can create an ODBC connection(DSN) on the 32-bit side of the system or on the 64-bit side of the system. 32-bit applications will only see ODBC connections created in the 32-bit side, and 64-bits applications will only see ODBC connections from the 64-bit side. Each kind of application has its own registry.
To setup DSN for 32-bit application you must use either : the ODBC Extender function qConfigData or %WINDIR%SysWOW64odbcad32.exe
and for 64-bit application you must use: %WINDIR%System32odbcad32.exe
Question:
I have a winbatch script that I use to quickly defined new ODBC connection(s) on a Windows Server. So far everything is working just as expected on x32 platform but when I am executing the script on x64 platform then none of my ODBC connections are visible when using the standard Windows ODBC control panel. I have checked the registry and there is no trace of my conection(s) but when looking at the ODBC.INI then I can se my connections I can also see my connections when using the ODBC32 control panel. Then what can I do to have my ODBC connection(s) defined and visible when using the standard (x64) ODBC control panel? Obvioulsy Winbatch by default is not using the x64 ODBC management API...?Answer:
Sorry the ODBC Extender is 32 bit extender and doesn't currently support 64 bit ODBC operations. We do not currently offer 64 bit version of our extenders.User Reply:
I have hundreds DNSs and I wrote a small winbatch program to automatically add these DSNs to my servers. Any idea on what to do with a x64 system?Answer:
Because the ODBC Extender is compiled as a 32 bit DLL, it acts as a 32 bit App. All of the ODBC operations are treated as 32 bit operations on 64 bit platform. The ODBC Extender would have to be compiled as a 64 bit Dll in order to have the qConfigData create 64 bit DSNs. That is not likely to happen any time soon.If you must create 64 DSNs you will need to find a workaround...
- Option 1 (easiest):
Use Microsofts 64 bit ODBC Driver Configuration Program: odbcconf.exe http://support.microsoft.com/kb/313008 - Option 2:
ODBC DSNs are specific connection configurations that are stored in the registry for a given driver. Luckily the Registry functions in WinBatch can be used to write values to the 64 bit registry. Check out the following tech support artile from Microsoft that details how to programmatically create a DSN in the registry. http://support.microsoft.com/kb/184608I suppose, you could try to reproduce this code in Winbatch.
Article ID: W17585
Filename: ODBC on 64 bit System.txt
File Created: 2019:05:09:08:59:40
Last Updated: 2019:05:09:08:59:40