How can i make Connection object to use an .UDL or .DSN file rather than
connection string ?
> > How can i make Connection object to use an .UDL or .DSN file rather
> > than connection string ?
> odb.connectionstring="File Name=Whatever.UDL;"
Could you tell me why ?
Because we are going to heavily relay on that.
> Sorry, I don't use the DE and my general advice would be to abandon that.
The DE is a thin wrapper around ADO and gets you very little over using ADOQuote:> Could you tell me why ?
> Because we are going to heavily relay on that.
It's also not going to be supported beyond VB6 so it's definitely a dead end
I read in the Bill Vaughn book, ADO Examples and Best Practices, that after
an ADO connection object uses a UDL file for it's connectionstring, it somehow
caches the file so it doesn't have to go to the file system each time a new
connection is opened using the same file. He didn't go into much detail and I
haven't been able to find any other documentation about this to support his
claim. In a DevelopMentor class I attended in August 2000, Ted Pattison
suggested the same, but mentioned only that he had heard this was the case and
hadn't yet researched it to find out if it was true.
In an article on ExtremeTech.com, it is said that, "File DSNs are especially
slow and not at all recommended for high-traffic sites because of the way the
files are handled -- each transaction requires that the file be opened,
read/written, closed, and republished to the data provider."
Can anyone confirm whether or not ADO does indeed cache UDL files and if so,
include a link to some documentation? Other than Bill's book, I haven't found
any documentation to support the caching claim.
The ExtremeTech article can be found here: