Without any provocation that I can think of, I got the message above after
opening my database this morning. The message further states that the only
way that the database can be opened is to delete the VBA project and all code
from modules, forms, and reports. This is a highly undesirable option. Yes,
I do have backups I can resort to, but I'd rather not if there is a
workaround.
The database has a meager bit of VBA associated with some forms and reports,
and I hadn't touched any of it for some time. Has anybody seen this error?
Access help was not helpful.
|
|
0
|
|
|
|
Reply
|
 Utf
|
11/15/2007 1:58:01 AM |
|
AccessMan <AccessMan@discussions.microsoft.com> wrote:
>Without any provocation that I can think of, I got the message above after
>opening my database this morning. The message further states that the only
>way that the database can be opened is to delete the VBA project and all code
>from modules, forms, and reports. This is a highly undesirable option. Yes,
>I do have backups I can resort to, but I'd rather not if there is a
>workaround.
I don't ever recall seeing this particular message although my memory
isn't perfect.
1) Make a copy
2) Try importing all the objects into a new database
3) Try a decompile. http://www.granite.ab.ca/access/decompile.htm
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
|
|
|
0
|
|
|
|
Reply
|
Tony
|
11/15/2007 2:55:22 AM
|
|
Tony:
Thanks for the response. Just to clarify, do you mean for me to import the
objects from the troubled database (or a copy of it) into a blank one? Does
the fact that the troubled database had not been compiled change anything?
"Tony Toews [MVP]" wrote:
> AccessMan <AccessMan@discussions.microsoft.com> wrote:
>
> >Without any provocation that I can think of, I got the message above after
> >opening my database this morning. The message further states that the only
> >way that the database can be opened is to delete the VBA project and all code
> >from modules, forms, and reports. This is a highly undesirable option. Yes,
> >I do have backups I can resort to, but I'd rather not if there is a
> >workaround.
>
> I don't ever recall seeing this particular message although my memory
> isn't perfect.
>
> 1) Make a copy
>
> 2) Try importing all the objects into a new database
>
> 3) Try a decompile. http://www.granite.ab.ca/access/decompile.htm
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>
|
|
|
0
|
|
|
|
Reply
|
Utf
|
11/15/2007 3:57:00 AM
|
|
AccessMan <AccessMan@discussions.microsoft.com> wrote:
>Thanks for the response. Just to clarify, do you mean for me to import the
>objects from the troubled database (or a copy of it) into a blank one?
Yes.
>Does
>the fact that the troubled database had not been compiled change anything?
No.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
|
|
|
0
|
|
|
|
Reply
|
Tony
|
11/15/2007 5:20:12 AM
|
|
Sadly, I encountered the same error message after initiating the import.
"Tony Toews [MVP]" wrote:
> AccessMan <AccessMan@discussions.microsoft.com> wrote:
>
> >Thanks for the response. Just to clarify, do you mean for me to import the
> >objects from the troubled database (or a copy of it) into a blank one?
>
> Yes.
>
> >Does
> >the fact that the troubled database had not been compiled change anything?
>
> No.
>
> Tony
>
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>
|
|
|
0
|
|
|
|
Reply
|
Utf
|
11/15/2007 1:32:02 PM
|
|
|
4 Replies
1858 Views
(page loaded in 2.987 seconds)
Similiar Articles: cannot open database because VBA project cannot be read ...Without any provocation that I can think of, I got the message above after opening my database this morning. The message further states that the onl... VBA Project Deleted - microsoft.public.access.modulesdaovba ...When I tried to open a module I had written, I got the following message: The database cannot be opened because the VBA project contained in it cannot be read. The database cannot be opened... - microsoft.public.access ...cannot open database because VBA project cannot be read ... Without any provocation that I can think of, I got the message above after opening my database this morning. Cannot open database requested error - microsoft.public.crm ...... public.project It displays the error message 'Project cannot recognise this file > format. ... cannot open database because VBA project cannot be read ... Cannot open ... Cannot open Project 2007 file, Project 2007 often tries 2 reinstal ...cannot open database because VBA project cannot be read ..... open project file - microsoft.public.project cannot open database because VBA project cannot be read ... The record cannot be deleted because it is read-only. - microsoft ...cannot open database because VBA project cannot be read ... The record cannot be deleted because it is read-only. - microsoft ... While running the ... cannot open ... Cannot update. Database or object is read-only (re-post ...Database or object is read-only (re-post ... cannot open database because VBA project cannot be read ... Cannot update. Database or object is read-only (re-post ... cannot ... Cannot open earlier version of access database - microsoft.public ...cannot open database because VBA project cannot be read ... Cannot open earlier version of access database - microsoft.public ... cannot open database because VBA project ... cannot access database - microsoft.public.access.conversion ...cannot open database because VBA project cannot be read ... Without any provocation that I can think of, I got the message above after opening my database this morning. Who's got the database open? - microsoft.public.access ...cannot open database because VBA project cannot be read ... cannot open database because VBA project cannot be read ... When I tried to open a module I had written, I got ... Microsoft Office Access 2010 - Database cannot open because VBA ...Microsoft Office Access 2010 - Database cannot open because VBA project cannot be read cannot open database because VBA project cannot be read>Without any provocation that I can think of, I got the message above after >opening my database this morning. The message further states that the only The database cannot be opened because the VBA project contained in ...Everytime my network goes down, power goes out, or computer turns off while my database is open, I get the message: "The database cannot be opened because ... Error message when you run a compiled Microsoft Access MDE, ACCDE ...... cannot be opened because the VBA project contained in it cannot be read. The database can ... before attempting to open the database and delete the VBA project. ... cannot open database because VBA project cannot be readdatabase.itags.org: Microsoft Access question: cannot open database because VBA project cannot be read, created at:Fri, 30 May 2008 19:45:00 GMT with 604 bytes, last ... 7/24/2012 1:05:35 PM
|
Search |
Post Question |
Groups |
Stream |
About |
Register
72 followers. 