> > Just my opinion, but I don't think this is good advice. For > one, it creates extra administration on the system, by > forcing the user/programmer /sysadmin/webadmin to create an > ODBC DSN setting for every new setup. For two, DBI and ODBC > both support dynamic DSNs, so why not use them?
If you have separate development, test and production environments, it's sometimes easier to use DSNs. That way, when you migrate from dev to test, for example, you automagically get the test environment connection information. That's one reason why I like DSNs over putting them in the code. Of course, TMTOWTDI... Jeff
