D
doug
hello all,
my client has purchased a third party COM object. my directive is to wrap
this up in a web service to save on licensing cost as this will need to be
accessed from 2+ machines.
this COM object uses ODBC to connect to a sql server. i know this as it
requires a data source of a select name on the machine.
i wrapped this up using interop and a class library in .Net.
when i instantiate this class in a web form or console where i have been
testing, all is good. when i instantiate this under a web service (worker
process). the calls to this objects connection method all fail!
i am confident it is using SQL Security as the connection properties ask for
a userid and password.
any thoughts as to what may be missing in the architecture?
thanks for reading.
Doug
my client has purchased a third party COM object. my directive is to wrap
this up in a web service to save on licensing cost as this will need to be
accessed from 2+ machines.
this COM object uses ODBC to connect to a sql server. i know this as it
requires a data source of a select name on the machine.
i wrapped this up using interop and a class library in .Net.
when i instantiate this class in a web form or console where i have been
testing, all is good. when i instantiate this under a web service (worker
process). the calls to this objects connection method all fail!
i am confident it is using SQL Security as the connection properties ask for
a userid and password.
any thoughts as to what may be missing in the architecture?
thanks for reading.
Doug