>>Ooops! Right. Well, lets go at it a different way then. There's really only one reason a dialog would pop up and that's due to an authentication challenge. When you set up your DSN, did you tell it to use SQL Server's authentication instead of NT's?
>>
>Yes,
>I use the SQL Server's authentication.
>Why would this be a problem?
IIS users a special user ID, IUSR_YourServerName, to gain access to web sites. If you had not specified SQL Server authentication in the ODBC setup, IIS would have passed the special ID to SQL Server for access. Unless you specifically added it, SQL Server would issue an authentication challenge. Remember that your DLL is running in the IIS process.
Having said this, something else just occured to me. Do you have any ASPs that access the SQL Server data via ADO? If not, how is your SQL Server security set up? ASP can only deal with SQL Server if the security is set up as Standard. If its Mixed or Integrated, it won't work. I assume this is due to what I discussed above about IIS's special anonymous user ID.
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
