EDN Admin
Well-known member
We have found an issue with deployment of a standalone VB application (no external files) that connects to a SQL Server database (SQL 2008 R2). We have distilled the problem to the following:
<pre>Sub Main
Dim cnnDB As NEW ADODB.Connection
On Error GoTo ErrorHandler
cnnDB.Open "Provider=SQLOLEDB;Data Source=server;Initial Catalog=database;UID=user;PWD=pass;"
MsgBox "Opened"
Exit Sub
ErrorHandler:
MsgBox Err.Description
End Sub[/code]
When run locally (Win7/SP1) we get the "opened" message box. When deployed (via file copy) to a Windows 2008 server we get "Class does not support Automation or does not support expected interface". Curious thing is that on Tuesday (prior to
SP1 being installed on this machine) it all worked - we could simply copy the resulting executable to the server no problems; since applying SP1 (Wednesday morning) we keep getting this error.
I have now confirmed that this is indeed the case by compiling in Windows XP Mode on the same Windows 7 box and sending the resulting file to the server - the code worked when run locally and also on the server.
I would have to say that this has arisen because of "something" in SP1 - but what exactly that something is...
View the full article
<pre>Sub Main
Dim cnnDB As NEW ADODB.Connection
On Error GoTo ErrorHandler
cnnDB.Open "Provider=SQLOLEDB;Data Source=server;Initial Catalog=database;UID=user;PWD=pass;"
MsgBox "Opened"
Exit Sub
ErrorHandler:
MsgBox Err.Description
End Sub[/code]
When run locally (Win7/SP1) we get the "opened" message box. When deployed (via file copy) to a Windows 2008 server we get "Class does not support Automation or does not support expected interface". Curious thing is that on Tuesday (prior to
SP1 being installed on this machine) it all worked - we could simply copy the resulting executable to the server no problems; since applying SP1 (Wednesday morning) we keep getting this error.
I have now confirmed that this is indeed the case by compiling in Windows XP Mode on the same Windows 7 box and sending the resulting file to the server - the code worked when run locally and also on the server.
I would have to say that this has arisen because of "something" in SP1 - but what exactly that something is...
View the full article