DSN Versus DSN-less

[neemi]

ACCESS/SQL SERVER

I just wanted to start up a thread so i can see what peoples experience's are with working with DSN or DSN-Less connections. Pro's and Con's. Re. Speed etc.
As I have generally used DSN as this is all I have really known, but recently came accross using DSN-Less as suggested by a friend.

I can see that using DSN-Less already has an advantage that nothing needs to be set up on the user machine. ie. the DSN.

But wanted to almost get a debate going for a learning purpose. Does it have any more pruposeful advantages/disadvantages etc.

Cheers,
Neemi

 

[lameid]

I don't have much experience with it but I did realize that Access treates file and system ODBC DSN's differently. With one it takes the connection string infation out of the DSN and your object is portable. I forget which is which but I think the file dsn gives you the portable functionality.

My expectation is that there would be little or no difference in speed.

 

[BobRodes]

Then, you can also get out of ODBC altogether....

 

[lameid]

Then, you can also get out of ODBC altogether....

What? Either you need ODBC or you don't. If you do, either you need a stored DSN or you don't.

 

[cmmrfrds]

I would go with the DSN-less connection since it is easier to maintain and the app is more portable. The only problem may be an older MDAC library on some PC's that you are copying the app to, but these should have the same or newer version anyway. No disadvantages that I can think of.

If you want some code that will link all the sql server tables from a database let me know.

 

[BobRodes]

<Either you need ODBC or you don't.

That suggests that there are no alternatives to using ODBC in situations where ODBC would work. I disagree....