Missing Access Driver in ODBC 1

[eamc]

I have Win2k Pro OS Version 5.0 (Build 2195; Service Pack2), and a MS Access-based program that will not run because my ODBC lasks an Access Driver. In Win2k I go Control Panel > Administrative Tools > Data Sources (ODBC): Now I see only CC_LOCAL_DSN_1 Intersolv 3.00 32-bit Paradox File (*.db); dBase files MS dBase driver (*.dbf); Excel files Microsoft Excel Driver (*.xls); FoxPro files MS FoxPro driver (*.dbf); and Text files MS Text driver (*.txt, *.csv) - I do not see any DCI Access files that can be added after pushing ADD button.

Starting with W2k, MS Access Components are distributed as part of the operating system service packs. I reinstalled my win2kSP2.exe, but no help.

How do I get an Access driver in there? My W95 computer has it.

Edwin

 

[pbxman]

Install MS Access or go to

http://www.microsoft.com/data/download.htm

and download MDAC. Go back in and if you dont see it, click "add" in user DSN and specify what you want to add.

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[eamc]

MS Access already installed on my machine and working fine - it can access .mdb files. It is just in Windows ODBC that the driver is missing, therefore ImageAXS cannot access .mdb. Should I un- and re-install MS Access or just reinstall it? What is MDAC?

Thanks,

Edwin

 

[pbxman]

so you open ODBC in administrative tools...and do not see .mdb extension under user OR system DSN?

If you click "add" on the left..can you find a Microsoft Access driver there? pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[eamc]

Hi pbxman,

Thanks for your speedy answer!

The answer is NO to both of your questions - no .mdb anywhere in user, system, or ADD - details in my original post. I did download the MDAC corresponding to WS2k SP2 (2.5 mdac_typ.exe) and when trying to install it just now, got the message that it was already installed. Remember - I reinstalled W2ksp2.exe a long time ago. What to do?

Edwin

 

[pbxman]

2 more things..

1) Go to c:\winnt\system32 and check the version of the ODBCJT32.dll file.

2) Slick on system DSN in ODBC configuration - is there an AMSDB entry? Go to C:\WINNT\System32\AMS_II to see if there is one present.

3) Reinstall Office or MSAccess selecting "install all from local computer"

If you're an admin on the pc, you're showing all files, and you still cant see it...Im stumped. The fox Pro and Excel driver is the same used for .mdb files. It's MSJet 3.5 that contains the ODBCJT32.dll file (which is part of MDAC).

As a last resort if all else fails (before reinstalling 2K again) - download (from the same site you got 2.5 from):
MDAC 2.6, and MSJet 4.0SP3. MDAC 2.6+ does not contain the Jet components, and must be installed separately. Personally - i think something else is awry, but i cant seem to pinpoint it.

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[eamc]

Hi Pbxman (thanks for all your suggestions!)

Your #1) ODBCJT32.dll dated 5/4/2001 is in both c:\]winnt\system32\ and in \winnt\ServicePackFiles\i386 This is the same date as the one on the .dbf .xls .csv drivers in ADD under ODBC

Your #2) System DSN is totall empty: no AMSDB entry - nothing present, no source. If I click ADD, the same 7 drivers I mentioned appear. There is no file AMS_II in \winnt\system32
Your 3) Reinstalled Access 97 from CD (through Control Panel) - no soap

What about the ODBC Paradox Driver setup that asks for data source, description, and database directory? What about CONFIGURE in the ODBC panel?

Have not yet downloaded MDAC 2.6, but want to mention that the inability to run this program using .mdb files occurred after a very agitated installation, un- and re-installation etc. of Corel Word Perfect 10 which caused some WinDoctor troubles with WP files. At the beginning of this installation the WP guy had me remove a Borland entry from the registry. I still have the oldreg.reg that precedes that, but believe that the Borland entry was restored anyway when WP8 was reinstalled. Do you think this has anything to do with the ODBC trouble?

Thanks again for your excellent help!

Edwin

 

[pbxman]

Absolutely i think it would interfere. Wordperfect uses ODBC as well, and if the install got botched, and registry settings were wiped out, then you're a prime candidate for trouble.

The problem with messing with ODBC is that they are hard-linked in Windows. You cant just copy files and delete as you can with other files (with regards to ODBC). Also - you mentioned you loaded Access 97..is there a reason you are using access 97? Those drivers are pre-windows 2000 and are not what you would load unless you specifically need Access97 drivers (MDAC 2.1). I was referring to Access 2000.

Either way - the driver appears to be on your pc..the only thing i would try (and its a longshot) is this:
in C:\winnt - open ODBCinst.ini and look for this line:

MS Access Database=Microsoft Access Driver (*.mdb) (32 bit)

If it's there, open ODBC.ini and verify it's listed under ODBC 32bit DataSources. If it isn't, add it, reboot, and try control panel/ODBC again. If after a reboot it is still not there, i would reinstall the OS because you have some serious problems that i bet MS wouldn't be able to figure out even after spending $1000 on phone-support

It stinks, but I cant think of any worthwhile fix for this that would fare better than reinstalling the OS with Access 2000+ only.
Sorry - good luck though! pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[eamc]

Hi Pbxman

I will try your recommendation. In the meantime, 5 questions:

1) You don't seem worried about the missing c:\winnt\system32\AMS_II ?

Idea 2) I have a total backup of everything about two months before the WP installation trouble. If I RESTORED not the registry, but just the files involved in ODBC drivers, which ones should I restore?

Idea 3) I could also restore the registry backed up just hours before the WP installation, just double-clicking the oldreg.reg I saved in c:\ If I did that, should I uninstall the WP10 first?

Idea 4) I could also restore everything (files AND registry) from the 2-month old backup. In that case, would I have first to uninstall programs installed after that date?

Idea 5) I had heard that Win2k had "repair" possibilities without wiping out all applications?

Sorry to be hitting you with so many questions, but your help is the best one I have. Thanks again!

Edwin

 

[pbxman]

eamc,

1) wasnt worried about it after you informed me about WP10. I think that is the cause of your problems.

2)By backup do you mean a complete copy of all files and folders on your pc a.k.a. "windows backup" or by a 3rd party backup software?

3) Go ahead and restore the registry you saved before WP10. It's worth a shot, but i think installing WP10 overwrote files you needed. Uninstalling WP10 will not restore your previous working .dll files that it overwrote. That is why a restore/rebuild is in order. But - like i said..its worth a shot at this point because you're a fish out of water with the pc in it's current state.

4) Depends on your backup software. Some allow a full system restore including only what you have in the backup, others will restore only what was backed-up and leave the rest alone. Full backups should completely restore ONLY what is on the backup.

***Note**restores are usually performed on fresh OS installs anyway. You would ideally reinstall Win2K, then restore from backup to get to your point 2 months ago.

5)Dont worry about the repair, its not going to fix your situation any better than a restore would.

If it were me, I would first save everything specific to programs you have currently...word docs, excel docs, pictures, etc. and reinstall windows 2K SP2. It only takes about 30 min.

In effect..you want to revert 100% to the time when everything was working perfectly.
pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[eamc]

Hi Pbxman

In your 4/19 message, you asked me to look for a specific line in ODBCinst.ini abd ODBC.ini There is no line exactly like what you wrote, but here is what is in the two files. BTW, I have backups of all these files from 1 month before the installation trouble, and could overwrite:

ODBCINST.INI contains:

[SQL Server (32 bit)]
Driver=c:\winnt\system32\\SQLSRV32.dll
Setup=c:\winnt\system32\\SQLSRV32.dll
32Bit=1
[ODBC 32 bit Drivers]
SQL Server (32 bit)=Installed
Microsoft Access Driver (*.mdb) (32 bit)=Installed
Microsoft Text Driver (*.txt; *.csv) (32 bit)=Installed
Microsoft Excel Driver (*.xls) (32 bit)=Installed
Microsoft dBase Driver (*.dbf) (32 bit)=Installed
Microsoft Paradox Driver (*.db ) (32 bit)=Installed
Microsoft Visual FoxPro Driver (32 bit)=Installed
Microsoft FoxPro VFP Driver (*.dbf) (32 bit)=Installed
Microsoft dBase VFP Driver (*.dbf) (32 bit)=Installed
Microsoft Access-Treiber (*.mdb) (32 bit)=Installed
Microsoft Text-Treiber (*.txt; *.csv) (32 bit)=Installed
Microsoft Excel-Treiber (*.xls) (32 bit)=Installed
Microsoft dBase-Treiber (*.dbf) (32 bit)=Installed
Microsoft Paradox-Treiber (*.db ) (32 bit)=Installed
Microsoft Visual FoxPro-Treiber (32 bit)=Installed
Driver do Microsoft Access (*.mdb) (32 bit)=Installed
Driver da Microsoft para arquivos texto (*.txt; *.csv) (32 bit)=Installed
Driver do Microsoft Excel(*.xls) (32 bit)=Installed
Driver do Microsoft dBase (*.dbf) (32 bit)=Installed
Driver do Microsoft Paradox (*.db ) (32 bit)=Installed
Driver para o Microsoft Visual FoxPro (32 bit)=Installed
Microsoft ODBC for Oracle (32 bit)=Installed
Microsoft FoxPro Driver (*.dbf) (32 bit)=Installed
[Microsoft Access Driver (*.mdb) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odbcjt32.dll
32Bit=1
[Microsoft Text Driver (*.txt; *.csv) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odtext32.dll
32Bit=1
[Microsoft Excel Driver (*.xls) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odexl32.dll
32Bit=1
[Microsoft dBase Driver (*.dbf) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\oddbse32.dll
32Bit=1
[Microsoft Paradox Driver (*.db ) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odpdx32.dll
32Bit=1
[Microsoft Visual FoxPro Driver (32 bit)]
Driver=C:\WINNT\System32\vfpodbc.dll
Setup=C:\WINNT\System32\vfpodbc.dll
32Bit=1
[Microsoft FoxPro VFP Driver (*.dbf) (32 bit)]
Driver=C:\WINNT\System32\vfpodbc.dll
Setup=C:\WINNT\System32\vfpodbc.dll
32Bit=1
[Microsoft dBase VFP Driver (*.dbf) (32 bit)]
Driver=C:\WINNT\System32\vfpodbc.dll
Setup=C:\WINNT\System32\vfpodbc.dll
32Bit=1
[Microsoft Access-Treiber (*.mdb) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odbcjt32.dll
32Bit=1
[Microsoft Text-Treiber (*.txt; *.csv) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odtext32.dll
32Bit=1
[Microsoft Excel-Treiber (*.xls) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odexl32.dll
32Bit=1
[Microsoft dBase-Treiber (*.dbf) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\oddbse32.dll
32Bit=1
[Microsoft Paradox-Treiber (*.db ) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odpdx32.dll
32Bit=1
[Microsoft Visual FoxPro-Treiber (32 bit)]
Driver=C:\WINNT\System32\vfpodbc.dll
Setup=C:\WINNT\System32\vfpodbc.dll
32Bit=1
[Driver do Microsoft Access (*.mdb) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odbcjt32.dll
32Bit=1
[Driver da Microsoft para arquivos texto (*.txt; *.csv) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odtext32.dll
32Bit=1
[Driver do Microsoft Excel(*.xls) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odexl32.dll
32Bit=1
[Driver do Microsoft dBase (*.dbf) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\oddbse32.dll
32Bit=1
[Driver do Microsoft Paradox (*.db ) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odpdx32.dll
32Bit=1
[Driver para o Microsoft Visual FoxPro (32 bit)]
Driver=C:\WINNT\System32\vfpodbc.dll
Setup=C:\WINNT\System32\vfpodbc.dll
32Bit=1
[Microsoft ODBC for Oracle (32 bit)]
Driver=C:\WINNT\System32\msorcl32.dll
Setup=C:\WINNT\System32\msorcl32.dll
32Bit=1
[Microsoft FoxPro Driver (*.dbf) (32 bit)]
Driver=C:\WINNT\System32\odbcjt32.dll
Setup=C:\WINNT\System32\odfox32.dll
32Bit=1


ODBC.INI contains:

[ODBC 32 bit Data Sources]
dBASE Files=Microsoft dBase Driver (*.dbf) (32 bit)
Excel Files=Microsoft Excel Driver (*.xls) (32 bit)
FoxPro Files=Microsoft FoxPro Driver (*.dbf) (32 bit)
Text Files=Microsoft Text Driver (*.txt; *.csv) (32 bit)
DeluxeCD=Microsoft Access Driver (*.mdb) (32 bit)
MS Access 97 Database=Microsoft Access Driver (*.mdb) (32 bit)
DCI Access=Microsoft Access Driver (*.mdb) (32 bit)
ECDCMusic=Microsoft Access Driver (*.mdb) (32 bit)
MQIS=SQL Server (32 bit)
CC_LOCAL__DSN_1=INTERSOLV 3.00 32-BIT ParadoxFile (*.db) (32 bit)
[dBASE Files]
Driver32=C:\WINNT\System32\odbcjt32.dll
[Excel Files]
Driver32=C:\WINNT\System32\odbcjt32.dll
[FoxPro Files]
Driver32=C:\WINNT\System32\odbcjt32.dll
[Text Files]
Driver32=C:\WINNT\System32\odbcjt32.dll
[DeluxeCD]
Driver32=C:\WINNT\System32\odbcjt32.dll
[MS Access 97 Database]
Driver32=C:\WINNT\System32\odbcjt32.dll
[DCI Access]
Driver32=C:\WINNT\System32\odbcjt32.dll
[ECDCMusic]
Driver32=C:\WINNT\System32\odbcjt32.dll
[MQIS]
Driver32=c:\winnt\system32\\SQLSRV32.dll
[CC_LOCAL__DSN_1]
Driver32=c:\program files\common files\borland shared\bde\\IVIDP13.DLL