Hi<BR>I prefer DSN less connection.<BR>DSN connection are very slow because they go through ODBC which then uses the Drivers to access the database.<BR><BR>When you use a DSN-LESS connection with ASP the Drivers are accessed directly and the performance increase can be dramatic on the server.<BR><BR>Check http://www.4guysfromrolla.com/webtech/070399-1.shtml<BR><BR>Priyan.
The reason that I prefer to use a DSN is that I find it easier to manage.<BR><BR>For example, I prefer to have the database sit outside of the structure of my virtual directory. That way I know that a visitor cannot browse there. Better still, with a DSN I don't have to care where the database resides. So I think that from a security point-of-view you would be better off using a DSN.<BR><BR>This time last year a lot of people wrote articles espousing(?) the benefits of a DSN-less connection, (some of them will even try to tell you that Session variables are evil ;)<BR><BR>However none of them can tell you that you will get a significant boost by using a DSN over non-DSN to connect to the database.<BR><BR>So, until one of my websites crashes from a lethal mix of Session variables and DSN's, I'll opt for practicality over technicality.<BR><BR>I hope this better explains my reasoning.<BR><BR>My 2 cents + 10% GST<BR><BR>HTH<BR><BR>Darren<BR>darren@showusyourc ode.com