Nevermind, I figured out, it should be DBConnection.Execute(Query to run)
Hi AlexKaras , I asked our database guy to take a look at my script below, and he doesn't know why it failed either. So my script is like this:
11 Sub try
12
13 Set AConnection = ADO.CreateConnection
14
15 AConnection.ConnectionString = "Provider=SQLNCLI11;data source=xxx-xxx-xxx.xx.xxxx.xxx;initial catalog=xxxxx;integrated security=true;multipleactiveresultsets=true;app=xxxxx;"
16
17 AConnection.Open
18
19
20 AConnection.Close
21
22 End Sub
Below is the error details returned:
VBScript runtime error.
Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Error location:
Unit: "E-Academy\E-Academy\Script\WilliamTestScript"
Line: 17 Column: 3.
Looks like it was complainting about line 17 - AConnection.Open
Can you please give more instruction how to fix it? BTW, do I have to have SQL server 20xx installed on the machine first in order to run the script? because currently I don't have it nor the Native Client on the machine.
Thanks!
Hi,
Does the same error occur if you remove 'multipleactiveresultsets=true;' from the connection string?
Hi AlexKaras I think I still need your help regarding this. Now I can setup the SQL connection, but when I tried to execute the query below, it returned me another error: "Object doesn't support named arguments: DBConnection.CommandText".
Set DBConnection = ADO.CreateConnection
DBConnection.ConnectionString = "Provider=xxxx;Integrated Security=xxxx;Persist Security Info=False;User ID=xxxx;Initial Catalog=xxxx;Data Source=xxxx"
DBConnection.Open
DBConnection.CommandText = "My Query to Run"
DBConnection.Execute()
DBConnection.Close
Nevermind, I figured out, it should be DBConnection.Execute(Query to run)
Yes, I removed 'multipleactiveresultsets=true;' from the connection string, and tried on both machines that have Native Client 11 and doesn't have Native Client 11.
It still returned the same VBScript runtime error "
Update, looks like the connection string I used was wrong. I take advantage of the wizard to build a connection string, and used it in the script, and it worked.
