Hi Alan,

The User DSN is only visible to the user who created it. The COM Object obviously runs under some other login. You can create System DSN but I would suggest to use DSN-less connections with SQLSTRINGCONNECT. This way you can eliminate one more external factor that could affect your application.

>I have created a MTDLL COM object which I am calling from an ASP page using the code
>Set oTest=Server.CreateObject("comtest.MyClass")
>oQuote = oTest.MyMethod(params list)
>
>When I call the method from within the VFP development environment everything works fine, and I get the expected results, but when I load the ASP page in a browser, I get an error due to a failed SQLCONNECT command...
>lnHandle = SQLCONNECT('ODBC Database name','Username','Password') (returns -1 to denote failed connection).
>
>AERROR() returns the following values
>[1]1526
>[2]Connectivity error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
>[3][Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
>[4]IM002
>[5]0
>[6]1
>[7].NULL.
>
>I cannot work-out why SQL finds the datasource when called from VFP, but cannot do so when called from the ASP page. Has anyone any ideas how I can solve this problem so that the COM object can run correctly from both environments?
>