Ok, I've been toying around with talking directly to the SQL database by
passing DSN's all together. BUT...here's the delima I'm running into:
>From what I understand about MS SQL you can assign a user to a database
and then if that user tries to access another database it wont let them.
Right? Well if that's the case when I let user1 access db1 only and
don't give user2 acess. In my ASP code I try to swap them around (just
to test them etc) and user2 also has access. HELP!

Scott 

Hi Scott,

How does your connection string look like? If you are using a DSN (not 
recommended though), you may have passed a user name and password to the 
DSN. Those will be used in your ASP app.....

Only when you use Integrated Security (through a DSN or a custom 
connection string (did I already mention that was the recommended way to 
go?)), you can have different users accessing the database. For that to 
work, you'll also need to disable Anonymous Access to the website through 
the IIS MMC.

I suggest you eloborate a bit about your setup and code.

Cheers,

Imar


> Ok, I've been toying around with talking directly to the SQL database by
passing DSN's all together. BUT...here's the delima I'm running into:
>From what I understand about MS SQL you can assign a user to a database
and then if that user tries to access another database it wont let them.
Right? Well if that's the case when I let user1 access db1 only and
don't give user2 acess. In my ASP code I try to swap them around (just
to test them etc) and user2 also has access. HELP!

Scott