Microsoft dBase Driver (*.dbf) (32 bit)=Installed Microsoft Excel Driver (*.xls) (32 bit)=Installed Microsoft Text Driver (*.txt *.csv) (32 bit)=Installed Microsoft Access Driver (*.mdb) (32 bit)=Installed BTW, I have backups of all these files from 1 month before the installation trouble, and could overwrite: 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. In effect.you want to revert 100% to the time when everything was working perfectly. If it were me, I would first save everything specific to programs you have currently.word docs, excel docs, pictures, etc.
You would ideally reinstall Win2K, then restore from backup to get to your point 2 months ago.ĥ)Dont worry about the repair, its not going to fix your situation any better than a restore would. ***Note**restores are usually performed on fresh OS installs anyway.
Full backups should completely restore ONLY what is on the backup. 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.
But - like i s worth a shot at this point because you're a fish out of water with the pc in it's current state. That is why a restore/rebuild is in order. Uninstalling WP10 will not restore your previous working. It's worth a shot, but i think installing WP10 overwrote files you needed. "windows backup" or by a 3rd party backup software?ģ) Go ahead and restore the registry you saved before WP10. I think that is the cause of your problems.Ģ)By backup do you mean a complete copy of all files and folders on your pc a.k.a. RE: Missing Access Driver in ODBC eamc (TechnicalUser)ġ) wasnt worried about it after you informed me about WP10. Please let Tek-Tips members know their posts were helpful. It stinks, but I cant think of any worthwhile fix for this that would fare better than reinstalling the OS with Access 2000+ only. 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 ) If it isn't, add it, reboot, and try control panel/ODBC again. If it's there, open ODBC.ini and verify it's listed under ODBC 32bit DataSources. MS Access Database=Microsoft Access Driver (*.mdb) (32 bit) In C:\winnt - open ODBCinst.ini and look for this line: I was referring to Access 2000.Įither way - the driver appears to be on your pc.the only thing i would try (and its a longshot) is this:
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). You cant just copy files and delete as you can with other files (with regards to ODBC). The problem with messing with ODBC is that they are hard-linked in Windows.
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. Do you think this has anything to do with the ODBC trouble?Įdwin RE: Missing Access Driver in ODBC pbxman (MIS) 19 Apr 02 08:21Ībsolutely i think it would interfere. I still have the oldreg.reg that precedes that, but believe that the Borland entry was restored anyway when WP8 was reinstalled. At the beginning of this installation the WP guy had me remove a Borland entry from the registry. of Corel Word Perfect 10 which caused some WinDoctor troubles with WP files. mdb files occurred after a very agitated installation, un- and re-installation etc. Have not yet downloaded MDAC 2.6, but want to mention that the inability to run this program using. What about the ODBC Paradox Driver setup that asks for data source, description, and database directory? What about CONFIGURE in the ODBC panel? Your 3) Reinstalled Access 97 from CD (through Control Panel) - no soap
There is no file AMS_II in \winnt\system32\ If I click ADD, the same 7 drivers I mentioned appear. Your #2) System DSN is totall empty: no AMSDB entry - nothing present, no source. Your #1) ODBCJT32.dll dated is in both c:\]winnt\system32\ and in \winnt\ServicePackFiles\i386 This is the same date as the one on the. Hi Pbxman (thanks for all your suggestions!)