Hi,

I have a problem with a converted database. It never was locked before,
neither workgroup security has or had been applied.

But on the Access 2007 format, all VBA code is 'locked' and unviewable.

Unfortunately, I never have backed it up because after conversion, it has
worked for a while.

This must be a bug, because even a password for 'unlocking' never has been
asked.

Anyone a solution?

Thanks!

"Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
message news:7A6D297C-1B9F-43E7-91D1-(E-Mail Removed)...
> Hi,
>
> I have a problem with a converted database. It never was locked before,
> neither workgroup security has or had been applied.
>

ps: It is this 2003 problem
http://support.microsoft.com/kb/823225

But in 2007 it has become _worse_ since signing the db, does not solve the
problem.

Hi Egbert

Try setting the folder where you have this database as a Trusted Location
under:
Office Button | Access Options | Trust Center | Trust Center Settings.

Digital signing should work, though "conversion" may have affected it.

If you are familiar with Access, there's some general info on working with
the new version here:
Converting to Access 2007
at:
http://allenbrowne.com/Access2007.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
message
news:7A6D297C-1B9F-43E7-91D1-(E-Mail Removed)...
> Hi,
>
> I have a problem with a converted database. It never was locked before,
> neither workgroup security has or had been applied.
>
> But on the Access 2007 format, all VBA code is 'locked' and unviewable.
>
> Unfortunately, I never have backed it up because after conversion, it has
> worked for a while.
>
> This must be a bug, because even a password for 'unlocking' never has been
> asked.
>
> Anyone a solution?
>
> Thanks!

"Allen Browne" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Egbert
>
> Try setting the folder where you have this database as a Trusted Location
> under:
> Office Button | Access Options | Trust Center | Trust Center Settings.

Hello my friend,

I have found this already but did not make any difference.

The pointis, that VBA -thinks- it is locked or protected by a password, but
in reality it never was!

This happens as follows

Sign a mdb on 2003 (maybe this step is not related however).
convert it to 2007
Modify the code. Now a warning will say that the certificate will void (or
something).
Accept the change

Now you never are allowed to modify the code again. However, the certificate
is gone as well.

I found an old copy of the 2003 version, and will export the code from there
and create a total clean new database and import.

Interesting.

I don't have a setup I can test for that.
I wonder if anyone else has experienced this.
Hopefully you will get other replies here.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
message
news:Ozo$(E-Mail Removed)...
>
> "Allen Browne" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Egbert
>>
>> Try setting the folder where you have this database as a Trusted Location
>> under:
>> Office Button | Access Options | Trust Center | Trust Center Settings.
>
> Hello my friend,
>
> I have found this already but did not make any difference.
>
> The pointis, that VBA -thinks- it is locked or protected by a password,
> but in reality it never was!
>
> This happens as follows
>
> Sign a mdb on 2003 (maybe this step is not related however).
> convert it to 2007
> Modify the code. Now a warning will say that the certificate will void
> (or something).
> Accept the change
>
> Now you never are allowed to modify the code again. However, the
> certificate is gone as well.
>
> I found an old copy of the 2003 version, and will export the code from
> there and create a total clean new database and import.

Is this all happening on the same PC, or are you using Access 2003 and
Access 2007 on different PCs?

--
Brendan Reynolds
Access MVP


"Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
message news:Ozo$(E-Mail Removed)...
>
> "Allen Browne" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Egbert
>>
>> Try setting the folder where you have this database as a Trusted Location
>> under:
>> Office Button | Access Options | Trust Center | Trust Center Settings.
>
> Hello my friend,
>
> I have found this already but did not make any difference.
>
> The pointis, that VBA -thinks- it is locked or protected by a password,
> but in reality it never was!
>
> This happens as follows
>
> Sign a mdb on 2003 (maybe this step is not related however).
> convert it to 2007
> Modify the code. Now a warning will say that the certificate will void
> (or something).
> Accept the change
>
> Now you never are allowed to modify the code again. However, the
> certificate is gone as well.
>
> I found an old copy of the 2003 version, and will export the code from
> there and create a total clean new database and import.
>
>
>
>

OK, never mind, I've tested it now and can confirm that it does happen on
one PC.

Code-signing is no longer supported when using the new ACCDB format, so you
might as well remove the sig before converting. It certainly is unfortunate
that the situation isn't handled more elegantly than this, though.

--
Brendan Reynolds
Access MVP


"Brendan Reynolds" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Is this all happening on the same PC, or are you using Access 2003 and
> Access 2007 on different PCs?
>
> --
> Brendan Reynolds
> Access MVP
>
>
> "Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
> message news:Ozo$(E-Mail Removed)...
>>
>> "Allen Browne" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Hi Egbert
>>>
>>> Try setting the folder where you have this database as a Trusted
>>> Location under:
>>> Office Button | Access Options | Trust Center | Trust Center Settings.
>>
>> Hello my friend,
>>
>> I have found this already but did not make any difference.
>>
>> The pointis, that VBA -thinks- it is locked or protected by a password,
>> but in reality it never was!
>>
>> This happens as follows
>>
>> Sign a mdb on 2003 (maybe this step is not related however).
>> convert it to 2007
>> Modify the code. Now a warning will say that the certificate will void
>> (or something).
>> Accept the change
>>
>> Now you never are allowed to modify the code again. However, the
>> certificate is gone as well.
>>
>> I found an old copy of the 2003 version, and will export the code from
>> there and create a total clean new database and import.
>>
>>
>>
>>
>
>

Brendan, thank you for following through on this, and Egbert thank you for
your post.

I am seeking the update my "Converting to Access 2007" article at:
http://allenbrowne.com/Access2007.html#Compatibility

Would this statement cover it accurately?
Do not convert a digitally signed database to an ACCDB.
Access 2007 will prevent you modifying the code if you do.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Brendan Reynolds" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> OK, never mind, I've tested it now and can confirm that it does happen on
> one PC.
>
> Code-signing is no longer supported when using the new ACCDB format, so
> you might as well remove the sig before converting. It certainly is
> unfortunate that the situation isn't handled more elegantly than this,
> though.
>
> --
> Brendan Reynolds
> Access MVP
>
>
> "Brendan Reynolds" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Is this all happening on the same PC, or are you using Access 2003 and
>> Access 2007 on different PCs?
>>
>> --
>> Brendan Reynolds
>> Access MVP
>>
>>
>> "Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
>> message news:Ozo$(E-Mail Removed)...
>>>
>>> "Allen Browne" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Hi Egbert
>>>>
>>>> Try setting the folder where you have this database as a Trusted
>>>> Location under:
>>>> Office Button | Access Options | Trust Center | Trust Center Settings.
>>>
>>> Hello my friend,
>>>
>>> I have found this already but did not make any difference.
>>>
>>> The pointis, that VBA -thinks- it is locked or protected by a password,
>>> but in reality it never was!
>>>
>>> This happens as follows
>>>
>>> Sign a mdb on 2003 (maybe this step is not related however).
>>> convert it to 2007
>>> Modify the code. Now a warning will say that the certificate will void
>>> (or something).
>>> Accept the change
>>>
>>> Now you never are allowed to modify the code again. However, the
>>> certificate is gone as well.
>>>
>>> I found an old copy of the 2003 version, and will export the code from
>>> there and create a total clean new database and import.

Well, I've only done the one quick test, but that seems to be the case, yes.
Of course, when you convert, the converted file is saved as filename.accdb,
and the original filename.mdb is left untouched, so all you have to do is
open the mdb file and remove the signature and convert again. No work should
be lost, provided you don't delete the original mdb.

--
Brendan Reynolds
Access MVP


"Allen Browne" <(E-Mail Removed)> wrote in message
news:u%(E-Mail Removed)...
> Brendan, thank you for following through on this, and Egbert thank you for
> your post.
>
> I am seeking the update my "Converting to Access 2007" article at:
> http://allenbrowne.com/Access2007.html#Compatibility
>
> Would this statement cover it accurately?
> Do not convert a digitally signed database to an ACCDB.
> Access 2007 will prevent you modifying the code if you do.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Brendan Reynolds" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> OK, never mind, I've tested it now and can confirm that it does happen on
>> one PC.
>>
>> Code-signing is no longer supported when using the new ACCDB format, so
>> you might as well remove the sig before converting. It certainly is
>> unfortunate that the situation isn't handled more elegantly than this,
>> though.
>>
>> --
>> Brendan Reynolds
>> Access MVP
>>
>>
>> "Brendan Reynolds" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Is this all happening on the same PC, or are you using Access 2003 and
>>> Access 2007 on different PCs?
>>>
>>> --
>>> Brendan Reynolds
>>> Access MVP
>>>
>>>
>>> "Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
>>> message news:Ozo$(E-Mail Removed)...
>>>>
>>>> "Allen Browne" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> Hi Egbert
>>>>>
>>>>> Try setting the folder where you have this database as a Trusted
>>>>> Location under:
>>>>> Office Button | Access Options | Trust Center | Trust Center Settings.
>>>>
>>>> Hello my friend,
>>>>
>>>> I have found this already but did not make any difference.
>>>>
>>>> The pointis, that VBA -thinks- it is locked or protected by a password,
>>>> but in reality it never was!
>>>>
>>>> This happens as follows
>>>>
>>>> Sign a mdb on 2003 (maybe this step is not related however).
>>>> convert it to 2007
>>>> Modify the code. Now a warning will say that the certificate will void
>>>> (or something).
>>>> Accept the change
>>>>
>>>> Now you never are allowed to modify the code again. However, the
>>>> certificate is gone as well.
>>>>
>>>> I found an old copy of the 2003 version, and will export the code from
>>>> there and create a total clean new database and import.
>

Thank you, Brendan.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Brendan Reynolds" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Well, I've only done the one quick test, but that seems to be the case,
> yes. Of course, when you convert, the converted file is saved as
> filename.accdb, and the original filename.mdb is left untouched, so all
> you have to do is open the mdb file and remove the signature and convert
> again. No work should be lost, provided you don't delete the original mdb.
>
> --
> Brendan Reynolds
> Access MVP
>
>
> "Allen Browne" <(E-Mail Removed)> wrote in message
> news:u%(E-Mail Removed)...
>> Brendan, thank you for following through on this, and Egbert thank you
>> for your post.
>>
>> I am seeking the update my "Converting to Access 2007" article at:
>> http://allenbrowne.com/Access2007.html#Compatibility
>>
>> Would this statement cover it accurately?
>> Do not convert a digitally signed database to an ACCDB.
>> Access 2007 will prevent you modifying the code if you do.