![]() |
to all MS SQL gurus
After 2 years of using a program, i suddenly got this error. I tried re-installing SQL but im still getting the message. Anyone encountered similar situation before?
----------------------------- Microsoft OLE DB Provider for ODBC Drivers error '80040e14' [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL xplog70.dll, or one of the DLLs it references. Reason: 193(error not found). |
bump
|
I don't know if this will help , here's what I found on google
Identity works with Access 2000 ONLY if you use the "Jet OLEDB Provider 4.0"! So define your ODBC connection not with "Microsoft Access Driver" but with "Jet OLEDB Provider 4.0". So your connection string should look like: "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Backup\OBS\Development\Db\obs2k.mdb;Pers ist Security Info=False" If you use a DSN-Less connection. Otherwise its in the ODBC Settings. |
... it took 2 years to mess up a microsoft product? ...surprising
"Reason: 193(error not found)." :1orglaugh |
Quote:
|
Did you try MSDN?
Google Groups sometimes can help more than just their search engine. However, my suggestion is to delete your DSN and rec-reate it. I've found that helps sometimes. Good luck! |
Installing the latest service pack should fix it. If it doesn't, or you already have it, grab the latest MDAC from microsoft.com: MDAC download
|
Quote:
"Please note that it may take anywhere from 3 to 9 hours for your message to appear on Google Groups. " :( |
|
Whats a guru?
|
Quote:
only serious post pls. tnx! |
|
Quote:
|
anymore bright ideas?
|
now im going insane... :helpme
|
last bump :helpme
|
All times are GMT -7. The time now is 03:50 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123