going dsn-less

  • Thread starter Thread starter John
  • Start date Start date
J

John

I am inheriting an access db that has been worked on since 1997.
Updated, enhanced, modified, etc since that time. It uses SQL Server
2005 as the backend for the db. There are parts of the front end that
use DSN connection and others that do not. I am aware of the site
that Doug Steele has with the dsn-less info, which I got a copy of.
But I am wondering just how difficult would it be to convert over to
dsn-less? What all would it entail beyond what is on the website?
What pitfalls should I lookout for? This inherited db is about 30mgs
in size (after compact and repair) and is very complex in nature. I
would like to get away from the dsn and actually make the
connection(s) more unified in nature. Going dsn-less, I think, is the
answer to what will be problems.

Thanks.
John
 
As you probably suspect, I use DSN-less 99.9% of the time. Once the
connections are established, there's no difference over having a DSN.
 
As you probably suspect, I use DSN-less 99.9% of the time. Once the
connections are established, there's no difference over having a DSN.

--
Doug Steele, Microsoft Access MVPhttp://www.AccessMVP.com/DJSteele
Co-author: Access 2010 Solutions, published by Wiley
(no e-mails, please!)







- Show quoted text -
Click to expand...

After reading the article, only 99.9%?
 
This inherited db is about 30mgs
in size (after compact and repair)
Click to expand...

Compact and repair doesn't necessarily clean out bits and peices of
compiled VBA code. And I doubt importing into a new database cleans
it up either although now that I think about it I don't know that I've
explicitly tried that. Thus we recommend doing a decompile on an
occasional basis. Some, such as David W Fenton more often.

Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
start-up times
http://www.granite.ab.ca/access/decompile.htm

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
..1% of the time, I know it's throw-away, so there's no real point in
changing it. <g>

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/djsteele
Co-author: "Access 2010 Solutions", published by Wiley
(no e-mails, please!)



As you probably suspect, I use DSN-less 99.9% of the time. Once the
connections are established, there's no difference over having a DSN.
- Show quoted text -
Click to expand...

After reading the article, only 99.9%?
 
Decompile or how to reduce Microsoft Access MDB/MDE size and
decrease start-up times
http://www.granite.ab.ca/access/decompile.htm
Click to expand...

For what it's worth, I consider the purpose of decompile to be to
keep the VBA project in good health. It's a maintenance routine for
me. The reduced size is a tiny side benefit, but not the main point.
Nowadays disk space is so plentiful that this is not really an
issue, and since Access front ends are only very seldom downloaded
over the Internet, front-end size is simply not that much of an
issue.
 
As you probably suspect, I use DSN-less 99.9% of the time. Once the
connections are established, there's no difference over having a DSN.
Click to expand...

One thing I'm curious about - if one is using sql server security, and
dsn-less connections, the authentication info is available to 'anyone'
with retail Access in a pass through query. If one uses a system dsn,
the password is not readily available. Or am I wrong about this?
 
mat said:
One thing I'm curious about - if one is using sql server security, and
dsn-less connections, the authentication info is available to 'anyone'
with retail Access in a pass through query. If one uses a system dsn,
the password is not readily available. Or am I wrong about this?
Click to expand...

Yet another reason why Trusted Connection is the way to go!
 
Yet another reason why Trusted Connection is the way to go!
Click to expand...

Yeah, when you can. I do a fair amount of cross domain stuff where that
isn't an option (unless there is some secret sauce that I don't know
about). BTW I saw the note on your dsn-less page re pswd stored in clear
text, so you already had that covered.
 
Back
Top