Hi All,

I wonder if any one can shed any light on this. I have encrytped my database
to ensure nobody breaks it, and I think I have done just that. I selected the
encrypt databse option, entered the password and verified it.

When i closed access and reloaded it, I put the password in as requested and
nothing happens. The password screen disappears and it loads the home page. I
can not access my databse now. Does anyone have any suggestions as my brain
hurts after hunting through all my Access 2007 books and the help options...

I would appreciate it... Many Thanks

Lee

Show quote Hide quote Lee,

What do you mean by "the home page"? Do you mean the startup form of your
database?

Apologies if I'm suggesting things you've already tried:

1. Hold down Shift whilst pressing OK after entering your password.
Providing you haven't disabled the Shift key bypass this may help you get to
your database window.

2. After carrying out step one press F11 - see if this brings up your DB
window.

3. If this fails close and re-open MS Access then re-open the database
whilst holding Ctrl and repeatedly tapping Break.

If the database really is corrupt you can either restore from the backup you
took before securing and encrypting (because you did take one...... didn't
you?), or the tried and tested import everything into a new MDB usually does
the trick.

Ed Metcalfe.

Hi Ed,

Thanks for the suggestions, unfortunately none of them worked... I do have a
back up from last saturday, it is only missing the few forms I created since
then, and it should only take a day to get it back up to speed.

Learning from my own mistakes I am afraid...

Thanks for your help...

Lee

Show quoteHide quote

Show quote Hide quote Lee,

Odd, I've never seen this problem before.

I'd be happy to take a look at it, if you want me to. You'd need to find an
FTP site to send it to. I find www.yousendit.com to be good for files under
100MB.

Ed Metcalfe.

Hi Ed,

I would like you to have a look, unfortunately we had started to enter
employee details in and I wouldn't want to risk there data being intercepted.

Thank fully I do have a back up to use, I need to do a bit of work on it
though as it isn't the complete version, but it should only take me a day or
so.

Thanks for the offer, it is appreciated!

Lee

Show quoteHide quote

Though I have no experience with A2007(presumed from somewhere in your post),
on previous versions of Access the "Encrypt Database" works just fine.

At the same time, I am used to, especially since A2000, keeping backups (well,
more earnestly than usual). Like, every hour or so during development. In
running production, these databases do not seem to be untowardly sensitive,
but they certainly are in development.

In short, if a conversion to/from "encrypted" failed, I would just shrug and
try it again from a backup. Only a consistent failure would make me "stand up
and take notice".

You'll be aware, I hope, that the in-built "Encryption" is of marginal value.
It prevents anyone using "System Dump" utilities to read data, but it does
nothing if they can gain valid access to your mdb/mde through Access itself.
Such as, for instance, if they broke the passwords.

I have also heard it claimed that "Access Encryption" "reduces performance by
up to 10%". Which sounds quite likely. However, my main performance issues
amount to much more than 10%! (and I do indeed encrypt databases, that is
in-built encryption, for the marginal advantage it may have when considering
utilities external-to-Access).

Just do it again! Either you just had a glitch, or Access has a bug. The
latter is hopefully reproducible. You should have done this anyway before
posting. If it's consistent, eliminate that it may be only on one of your
mdb's!!!

There are no other reports I can remember, no.

(backup from last week? In my current A2002, which may well be just my
machine, I backup during development every hour or whenever I complete some
aspect. Not just due to Access bugs <g>, but an hour later I might decide my
original code was better! <vbg>)

HTH
Chris

Show quoteHide quote

More ULS Problems
Access coding to VB
Security loose ends
Different Computer, Can't Open db with Same Username & Password
ULS Flaw?