Access Project Encryption

[Jeff Carver]

Why is it that I can't encrypt an Access project (.adp/.ade) like I can an
Access database (.mdb/.mde)? Yes, I understand that a project is a
front-end to a SQL Server database, and obviously SQL Server isn't going to
less Access encrypt anything -- but why can't the contents of the .adp file
itself be encrypted? Without encryption, the database connection info is
readily accessible to anyone with a hex editor. This makes absolutely no
sense to me! By changing startup options, prohibiting the user by
interrupting the autoexec macro by holding down the space bar, etc., I can
secure a compiled database pretty well (though of course the encrytion isn't
exactly terribly sophisticated, it's better than nothing), but not so with a
compiled project. What gives?

 

[David Watson]

IT Risk Management (Development and Operational)

I am trying to compile a list of the potential risks in an IT environment. I
have produced a list of 100 development and operational risks and wonder if
others are interested in this list, or better still, adding to the list.

The intention is to develop a comprehensive list to assist IT project
managers and operational support personnel.

David Watson
(e-mail address removed)
www.incom.com.au

 

[Jeff Carver]

It appears that my concerns were unfounded. After I compiled my
project, I opened the .ade file with a hex editor and searched for
text segments known to be in the connection string -- no hits.
Microsoft obviously got this one right. In the immortal words of
Emily Latella: "Never mind."