With the error he is getting he will not be able to do that trick.
This error was caused by the an update downloaded from
www.windowsupdate.com
It was either:
Security Update for Microsoft Data Access Components (823718)
OR:
Q282010: Recommended Update for Microsoft Jet 4.0 Service Pack 7 (SP7) - Windows XP
I know because I am having the same problem. Now my Outlook gives me
this error: "The procedure entry point GETIUMS could not be located in the dynamic link library MSDART.DLL" when it loads.
AND
SQL Server 2000 gives me this error:
"Unknown Error 8007007F" when I try to Return All Rows from Enterprise Manager.
Do you have any other help?
Quote:
quote:Originally posted by Jaeger
Well your connection string isn't specifying a Username/Password combo, nor is it specifying to use trusted connection.
Here's a cheat on how to get a good ADODB connection string:
1. Create a file called <something>.UDL
2. Double click on the file.
3. You'll get a dialog that will allow you do specify the driver and connection settings for a database, PLUS it will allow you to test those connection settings.
4. Save the file and open it up in Notepad, it will contain a complete connection string for the connection. This ensures that you have a valid connection string for the authentication type you want.
A couple of things to keep in mind since you are developing for both WinNT and Win98:
1. NT and 98 handle authentication differently, NT will try to pass the credentials of the Logged on user whenever sent a challenge( ie Trusted Connection). If the client or the Server is a member of a domain, and the other is not, then a trusted connection has to be set up manually (by using Net Use \\<Server> /U:<Domain>\UserName) and the connection has to be made from the Client to the Server.
2. Since you are not specifying an Authentication type in your connection string, Windows 98 will default to a Null-Pipes session connection to the SQL server, while NT will try to establish a trusted connection (and if the SQL server can't resolve the security account, it puts [NULL] in the name of the user account when returning an authentication error)
If you need authenticated access to the SQL server, and you need to use 98 and NT, then I would recommend using SQL Authentication instead of Windows Authentication for the DB access... The down side is that you have to Create SQL accounts for each User that needs access. Alternatively, you can specify the "UseTrustedConnection=true" (spelling?) option if there is a domain structure that all the computers log into, but you still need to give individual Users or groups rights to the database.
|
I'm all out of idea. 
