Encryption messed up

  • Thread starter Thread starter Andreas Y.
  • Start date Start date
A

Andreas Y.

I have been using an Access07 db since Office07 release and it was encrypted
with a password. I now copied it to a new file, made several changes but
after modifying my switchboard, (I am not sure if this was the cause though)
I started getting an error on startup about the code in the 'on open' event
procedure. I just copied over the following 2 functions from the previous
version which seemed exactly the same though:

Private Sub Form_Open(Cancel As Integer)
' Minimize the database window and initialize the form.

' Move to the switchboard page that is marked as the default.
Me.Filter = "[ItemNumber] = 0 AND [Argument] = 'Default' "
Me.FilterOn = True

End Sub

Private Sub Form_Current()
' Update the caption and fill in the list of options.

Me.Caption = Nz(Me![ItemText], "")
FillOptions

End Sub

After saving that, although the code was the same, the error disappeared. I
noticed that encryption was messed up but again I don't know if it was
caused after this or if it happened before.

When I tried to compact the db, it is asking me for a password, I enter the
pwd and it says it is not a valid pwd. If I open the db in exclusive mode,
instead of showing decrypt db, (which is the case with the original db), it
shows encrypt db, which means that the db is encrypted but it doesn't
realise it. If I select encrypt and enter a pwd, again it says it is not a
valid pwd.

Please give me some ideas because I have done much valuable work and fine
tuning which will be lost now.

With this opportunity, I would also like to express my disappointment on
office 07. I have been using it since beta and I now have retail version
with sp installed. To many problems, it crashes a lot, plus it is not usable
at all. My opinion, stick with 2003.
 
On Sat, 5 Jan 2008 19:46:16 +0200, "Andreas Y."

Try compiling the code (code window > debug > compile). Observe it
complains about FillOptions. Realize that this is a custom procedure
that should also be copied to the new file.
Repeat until no further compilation problems.

-Tom.
 
No problems with debugging. This is not my problem. My problem is that the
db is encrypted and it doesn't know it. I cannot decrypt it or re-encrypt it
and together I cannot fo many other things like compact, etc.



Tom van Stiphout said:
On Sat, 5 Jan 2008 19:46:16 +0200, "Andreas Y."

Try compiling the code (code window > debug > compile). Observe it
complains about FillOptions. Realize that this is a custom procedure
that should also be copied to the new file.
Repeat until no further compilation problems.

-Tom.

I have been using an Access07 db since Office07 release and it was
encrypted
with a password. I now copied it to a new file, made several changes but
after modifying my switchboard, (I am not sure if this was the cause
though)
I started getting an error on startup about the code in the 'on open'
event
procedure. I just copied over the following 2 functions from the previous
version which seemed exactly the same though:

Private Sub Form_Open(Cancel As Integer)
' Minimize the database window and initialize the form.

' Move to the switchboard page that is marked as the default.
Me.Filter = "[ItemNumber] = 0 AND [Argument] = 'Default' "
Me.FilterOn = True

End Sub

Private Sub Form_Current()
' Update the caption and fill in the list of options.

Me.Caption = Nz(Me![ItemText], "")
FillOptions

End Sub

After saving that, although the code was the same, the error disappeared.
I
noticed that encryption was messed up but again I don't know if it was
caused after this or if it happened before.

When I tried to compact the db, it is asking me for a password, I enter
the
pwd and it says it is not a valid pwd. If I open the db in exclusive mode,
instead of showing decrypt db, (which is the case with the original db),
it
shows encrypt db, which means that the db is encrypted but it doesn't
realise it. If I select encrypt and enter a pwd, again it says it is not
a
valid pwd.

Please give me some ideas because I have done much valuable work and fine
tuning which will be lost now.

With this opportunity, I would also like to express my disappointment on
office 07. I have been using it since beta and I now have retail version
with sp installed. To many problems, it crashes a lot, plus it is not
usable
at all. My opinion, stick with 2003.
Click to expand...
Click to expand...
 
Ok, I get it. There's no way to resolve this as usual. This is called bug. I
have regret using office07 as well as Expression Web. I guess I have to
redesign my db again. I hope I can turn it back to 2003 and redesign it
there. By the way, all bugs I discovered in both office07 and Expression web
are destructive and irreversible.
 
Back
Top