Access 2007 Encryption question

[David G.]

I rethought my original question (which did not receive any comments),
so I am reposting. I hope my revised question clarifies my concerns.

Assume I split an Access 2007 application into a front-end (user
interface and local tables) and a back-end (data tables). I don't hard
code the location of the back-end file because I don't know where it
will end up.

In the past I've used code that allows the user to navigate to the
back-end file and re-link the tables. (Once the tables are re-linked,
the code bypasses the re-linking process unless the back-end file is
moved to another location.

I was wondering what affect encrypting the back-end file will have on
my re-linking process.

It dawns on me that encrypting the database only prevents someone from
opening the file and extracting meaning information, it doesn't affect
the use of the data. Encrypting the back-end should not have any
effect on my re-linking process. I shouldn't need to have the
encryption password to access the data using the front-end.

Please comment.

THANKS!
David G.

 

[Tom van Stiphout]

On Sun, 26 Jul 2009 13:29:14 -0400, David G. <[email protected]>
wrote:

Per the help file you should encrypt both FE and BE. Then you delete
the linked tables and re-establish them. Access will prompt for the
password.
Then open the Immediate window and type something like this:
?currentdb.TableDefs("tblPeople").Connect
MS Access;PWD=123Abc;DATABASE=C:\be_encrypted.accdb

This also explains why the FE should be encrypted as well

To relink programmatically is no different then it was before: set the
Connect property, and call RefreshLink.

-Tom.
Microsoft Access MVP