1. How To Install Odbc Driver In Windows 7 64 Bit

Windows 7 x64 has a robust well developed ODBC connection client, but. Once you do this, pick the appropriate ODBC driver. To open the ODBC Data Source Administrator in Windows 10. On the Start page, type ODBC Data Sources. The ODBC Data Sources Destop App should appear as a choice. To open the ODBC Data Source Administrator in Windows 7. On the Start menu, click Control Panel. In Control Panel, click Administrative Tools. In Administrative Tools. In Windows 7, the Data Sources (ODBC). Upon clicking Add. The excel drivers I need is not listed in the data sources management console in my windows 7. The only driver showing up under ODBC administrator is SQL Server. How do I add other drivers? I bet you may be using a 64-bit windows. If so, you may try to use.

Active2 years, 9 months ago

I have an existing PHP script that needs to work with data from an Access db, and the machine it's on is migrating from Win2K to Windows 7. I looked around, and Microsoft seems to say that this is still available somewhere, but I can't find any solid information about how to actually get it.

It is not an option to migrate this to another db at the moment because of other dependencies.

1,6624 gold badges19 silver badges25 bronze badges

3 Answers

Use odbcad32.exe under %WINDIR%SYSWOW64, you will find all the 32bit drivers enumerated. I'm sure MS Access 32-bit ODBC driver is shipped.

-- http://social.msdn.microsoft.com/Forums/en-IE/sqldataaccess/thread/685eacc1-a670-42d4-8392-924230fa90cb

85.8k7 gold badges96 silver badges133 bronze badges

Did you actually Google 'get jet odbc driver for windows 7'? I did and I found a number of possibilities, though only one of them looks like it will work.

First off, keep in mind that Jet itself has shipped as part of the OS starting with Windows 2000, so all you need are the ODBC drivers themselves.

The third Google link, Information about Jet 4.0 Service Pack 8, allows you to get the Jet ODBC DLLs (you'd need to get the version for NT4). I worried that this installer might check the OS and prevent you from installing the files, but it just runs transparently on WinXP (I'd assume the same on Vista/7, but maybe not). Since the Jet files are protected OS files, there's no danger installing an older version (a computer that's been kept up-to-date with Windows Update will already have something higher than Jet SP8, but the ODBC drivers are apparently not shipped with the OS in Win7, so this should work). If you can't get them, I can install it on my old Win95 box and send you the ODBC-specific files.

You may also have to install MDAC 2.8 to make them work (though you could register them manually, there are still non-Jet ODBC files that are needed that may or may not be installed on Windows 7). So far as I can tell the MDAC 2.8 download will be required.

One last caveat, if it's 64-bit Windows 7, you may be out of luck if you're using the Jet ODBC driver from contexts that cannot use 32-bit components. There is no 64-bit Jet yet (that's coming with Office 2010, and is in beta). A recent SO discussion has the link to the beta of the 64-bit Jet drivers. I don't know if that includes 64-bit ODBC support or not, though I'd tend to think it doesn't.


How To Install Odbc Driver In Windows 7 64 Bit

21.3k3 gold badges38 silver badges53 bronze badges

Here are the five steps that I did.

  1. Regsvr32 c: WindowsSysWOW64odbcconf.dll

  2. Loaded and installed 2007 Office System Driver: Data Connectivity Components from here.C: UsersHomerDownloadsODBCDownload 2007 Office System Driver Data Connectivity Components - Microsoft Download Center - Download Details_aspx.mht

  3. To use Windows 7 32-bit subsystem. You need to use the ODBC control panel here. c:windowssysWOW64odbcad32.exe I used DSNLess so I did not need this. But it does work. The one in the system32 folder gives an errors if you try to use it.

  4. My DSNLess Connection stringDSN = 'Provider=Microsoft.ACE.OLEDB.12.0;DataSource=c: inetpubwwwrootDatabasegdbhelp.mdb'

  5. Gave the IIS_Iuser account READ and WRITE rights to edit and add on the gdbhelp.mdb database.

Peter O.
22.1k9 gold badges60 silver badges71 bronze badges

Not the answer you're looking for? Browse other questions tagged ms-accesswindows-7odbc or ask your own question.



Starting with Windows XP and Windows Server 2003, ODBC is included in the Windows operation system. You should only explicitly install ODBC on earlier versions of Windows.

This section describes how ODBC components are installed and removed. Because driver developers always install an ODBC component (their driver), they need to read this section. Application developers need to read this section only if they will ship ODBC components with their applications. ODBC components include the Driver Manager, drivers, translators, the installer DLL, the cursor library, and any related files. For the purposes of this section, ODBC applications are not considered to be ODBC components.

Windows xp professional 64 bit download iso deutsch advertising. Note

This section is specific to Microsoft Windows platforms. How ODBC components are installed on other platforms is platform-specific.

ODBC components are installed and removed on a component-by-component basis, not a file-by-file basis. For example, if a translator consists of the translator itself and a number of data files, these files are installed and removed as a group; they must not be installed and removed on a file-by-file basis. The reason for this is to make sure that only complete components exist on the system.

For purposes of installing and removing components, the following are defined to be ODBC components:

  • Core components. The Driver Manager, cursor library, installer DLL, and any other related files make up the core components and must be installed and removed as a group.

  • Drivers. Each driver is a separate component.

  • Translators. Each translator is a separate component.

With the support of Unicode in ODBC 3.5 and later, some consideration must be given to using OLE DB components with ODBC. The 1.1 version of the OLE DB Provider for ODBC was written to specific Unicode specifications within ODBC 3.0. Because these specifications changed in ODBC 3.5, it is necessary to have version 1.5 or later of the provider when using ODBC 3.5 and later. This section contains the following topics.