so check whether sqlsvr32.dll is in your package, or if it isn't, why
it's expected to be.
It turns out that the dialog was in fact revealing the error. The error was
"SQL Server does not exist or access is denied.".
I will try and figure how I can get the dialog not show the rather confusing
"[Microsoft][ODBC SQL Server Driver][Shared Memory]" to the user.
Will also investigate the sqlsvr32.dll in my package, cheers, Adrian
"alan" <nos...@nowhere.com> wrote in message
news:eF7FUIHJ...@TK2MSFTNGP04.phx.gbl...
Have you tried using (ie adding) the dialogs to the UI? The default ones
populate WISE_SQL_CONN_STR for you.
Hope this helps,
James
http://dotmsi.com