First off, if you are using SQL Server, use a connection string rather than a DSN, and use the OLEDB driver, not the ODBC.<br>
<br>
Next, when you are editing the database, you're doing it from the workstation, and when the asp page does it, it it running from the server. Interdev lets you specify different usernames and passwords for development and runtime. Open the global.asa file in the editor and check out the application level strings.<br>
<br>
Also, check the authentication type. I don't believe IIS can pass itself off as a user to SQL if you are using NT Challenge Response.<br>
<br>