I suggest that you use the 64-bit Registry Editor to export the following branches (where these entries tend to be found) - HKEY_LOCAL_MACHINE\Software\ODBC This Microsoft KB article may be sufficient to get you through these. NOTE: On your 64-bit Windows machine, there are naturally some complications tied to the 32-bit Registry. The corruption takes the form of entries containing this 4-character string - entries aren't visible anywhere except Registry export files - but they can lead to a number of undesired behaviors. You may be hitting an old but recurring issue with minor corruption in the Windows Registry. The difference is in their counterintuitive directory location - System32 (for 64-bit components) and SysWow64 (for 32-bit components). Note that both the 32-bit and 64-bit program are named the same, odbcad32.exe. Nothing you've said, in your comment below nor in your original problem statement, clearly indicates that you're using the 32-bit ODBC Administrator. I think this article on my employer's site, about using 32-bit ODBC on 64-bit Windows, may help you out. Does anyone have any ideas on how to get the values back into the odbcad32 applet? That will most likely fix the software problem as well. I was attempting to run this as a computer administrator so permissions shouldn't be an issue, and besides I checked to make sure that they weren't changed, but I still can't get it to work. The registry key is HKEY_LOCAL_MACHINE\Software\Wow6432Node\ODBC When I opened that up the values were there, they just weren't accessible to the odbcad32 or my own application. So I checked the registry to see if it was completely removed. I checked the C:\Windows\SysWow64\odbcad32.exe to see if there is a problem with the ODBC settings, and the ODBC connection was no longer visible. Now a few weeks after installation I get a report that the application is no longer connecting to the database. After installation everything was working fine. I have a Windows 7 64bit system that must run a 32bit application that accesses a MSSQL Server 2005 express via an ODBC connection.
0 Comments
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |