Everything was going along great this AM. Had to go to a meeting, so I
closed the application I was working on and went to the meeting. When I
returned, I got this "Project Locked" message when I tried to go into the VBA
editor.
I made several copies of the file, and have a backup from yesterday, but
have 3 hours of work in this and would rather not have to go back and
recreate several forms, reports, and queries. I then tried:
1. a compact and repair, no good.
2. JetComp, still no good
3. decompile, still no good
4. import into new db, still no good. Get a messag that I need a password
to import forms.
I thought I had seen a message about this a while back, but have not been
able to locate in the newsgroup or via Google.
Any help would be greatly appreciated.

Signature
HTH
Dale
Don''t forget to rate the post if it was helpful!
email address is invalid
Please reply to newsgroup only.
Roger Carlson - 14 May 2008 15:36 GMT
Two wild stabs:
1) Is it possible someone else has it open?
2) Go into Task Manger and see if Access is still open as a Process. If it
is, End the process.

Signature
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
> Everything was going along great this AM. Had to go to a meeting, so I
> closed the application I was working on and went to the meeting. When I
[quoted text clipped - 16 lines]
>
> Any help would be greatly appreciated.
a a r o n . k e m p f @ g m a i l . c o m - 14 May 2008 17:32 GMT
good stuff.
Yes-- Access has bugs-- where it is quite easy to have a secondary
copy of the application _open_ but invisible.
This is a classic DAO bug (not cleaning up variables-- which is _NOT_
a requirement of VB it is only a requirement for DAO-- a _VERY_ buggy
library); and it has not been fixed in the past decade.
This is just yet another symptom that 'everyone needs to move from
DAO'.
If an object library-- is too buggy for real world usage-- then upsize
to SQL Server and ADO.
Thanks
-Aaron
On May 14, 7:36 am, "Roger Carlson" <RogerCarl...@noemail.noemail>
wrote:
> Two wild stabs:
> 1) Is it possible someone else has it open?
[quoted text clipped - 40 lines]
>
> - Show quoted text -
Roger Carlson - 14 May 2008 17:45 GMT
Since the original post said nothing about DAO, I can't imagine why you're
blathering about it.

Signature
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com
good stuff.
Yes-- Access has bugs-- where it is quite easy to have a secondary
copy of the application _open_ but invisible.
This is a classic DAO bug (not cleaning up variables-- which is _NOT_
a requirement of VB it is only a requirement for DAO-- a _VERY_ buggy
library); and it has not been fixed in the past decade.
This is just yet another symptom that 'everyone needs to move from
DAO'.
If an object library-- is too buggy for real world usage-- then upsize
to SQL Server and ADO.
Thanks
-Aaron
On May 14, 7:36 am, "Roger Carlson" <RogerCarl...@noemail.noemail>
wrote:
> Two wild stabs:
> 1) Is it possible someone else has it open?
[quoted text clipped - 47 lines]
>
> - Show quoted text -
a a r o n . k e m p f @ g m a i l . c o m - 15 May 2008 00:47 GMT
uh.. because the 'I have a hidden instance of Access' is a DAO_BUG!!!
if your library is too buggy for real world usage-- then graduate to
ADO.
-Aaron
On May 14, 9:45 am, "Roger Carlson" <RogerCarl...@noemail.noemail>
wrote:
> Since the original post said nothing about DAO, I can't imagine why you're
> blathering about it.
[quoted text clipped - 5 lines]
>
> good stuff.
> Yes-- Access has bugs-- where it is quite easy to have a secondary
> copy of the application _open_ but invisible.
[quoted text clipped - 68 lines]
>
> - Show quoted text -
Dale Fye - 14 May 2008 17:40 GMT
Thanks for the reply, Roger.
1. No, it's sitting on my C: drive
2. Nope, that's not it either
I think it may have to do with a corrupt digital signature (they make us
digitally sign almost everything that will run code around here, including
working copies). I've given up and am starting over from last nights backup,
but would appreciate any more suggestions anyone has.

Signature
Dale
email address is invalid
Please reply to newsgroup only.
> Two wild stabs:
> 1) Is it possible someone else has it open?
[quoted text clipped - 21 lines]
> >
> > Any help would be greatly appreciated.
olhos bonitos - 14 May 2008 20:57 GMT
> Everything was going along great this AM. Had to go to a meeting, so I
> closed the application I was working on and went to the meeting. When I
[quoted text clipped - 16 lines]
>
> Any help would be greatly appreciated.
Chris O'C - 15 May 2008 16:54 GMT
Did you digitally sign an Access 2K format file? (Hint, don't do that!) If
you or someone else later opened a digitally signed file in Access 2K, it can
corrupt the VBA project.
You may be able to save the VBA project by opening the db in Access 2003 (or
maybe 2007 - haven't tried it myself), removing the digital signature, then
closing the db. Open it again with Access 2003, then close it, and you can
probably open it afterwards in Access 2K without problems.
If it's in Access 2K format and you're required to digitally sign every db,
recommend you create an Access 2003 format db and import all objects into it
from the original, then compile and compact, then digitally sign it. No more
Access 2K.
Chris
Microsoft MVP
>Everything was going along great this AM. Had to go to a meeting, so I
>closed the application I was working on and went to the meeting. When I
[quoted text clipped - 15 lines]
>
>Any help would be greatly appreciated.
Dale Fye - 15 May 2008 18:34 GMT
Thanks, Chris.
I'll keep this in mind.

Signature
HTH
Dale
Don''t forget to rate the post if it was helpful!
email address is invalid
Please reply to newsgroup only.
> Did you digitally sign an Access 2K format file? (Hint, don't do that!) If
> you or someone else later opened a digitally signed file in Access 2K, it can
[quoted text clipped - 32 lines]
> >
> >Any help would be greatly appreciated.