Access 2007 - Three Strange Problems - Help Please

[Dave]

I'm having three very unusual problems with Access 2007:

1. When I exit Access after making changes (forms or VB code) to any
database, I get a message that Aceess has encountered a problem and it
restarts. When I close it without making any changes, it works correctly.
2. When I enter the VB Code Editor and scroll the active window, the code
editor "locks up." I must make some other window or program active and then
return to the code editor to get it working again. This will repeat itself
often during a coding session.
3. I have the Access options set to "always use event procedures," but
Access continues to generate Emvbedded Macros instead of VBA code.

I have tried the following:

1. Compacting and repairing the database I was working on.
2. Tried other Access databases.
3. "Repairing" MS Office from the Control Panel (basically reloads MS
Office).
4. Searched all Microsoft support and knowledge base locations I could find
pertinent to Access 2007.
5. Searched the Access World Forums
(http://www.access-programmers.co.uk/forums/) for pertinent info.

These actions produce no results.

If anyone has any info about these issues, please advise.
If not, what is the best way to "report" these issues to Microsoft so I can
see if Microsoft has any insight into what is happening?

Thanks for any assistance.

Dave

 

[Allen Browne]

This could be due to several things. A decompile might be the solution.

Firstly, make sure you have added the folder where you database resides as a
trusted location:
Office Button | Access Options | Trust Center | Trust Center Settings

Here's a standard sequence that addresses several kinds of corruption. Try
it in order:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

7. Still in the code window, choose Options on the Tools menu. On the
General tab, make sure Error Trapping is set to:
Break on Unhandled Errors
and the Compile on Demand is unchecked.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
the code syntax is compilable, and the VBA options are set to show errors
and avoid this kind of corruption.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

 

[Latifa muhammad]

I'm having three very unusual problems with Access 2007:

1. When I exit Access after making changes (forms or VB code) to any
database, I get a message that Aceess has encountered a problem and it
restarts. When I close it without making any changes, it works correctly.
2. When I enter the VB Code Editor and scroll the active window, the code
editor "locks up." I must make some other window or program active and
then return to the code editor to get it working again. This will repeat
itself often during a coding session.
3. I have the Access options set to "always use event procedures," but
Access continues to generate Emvbedded Macros instead of VBA code.

I have tried the following:

1. Compacting and repairing the database I was working on.
2. Tried other Access databases.
3. "Repairing" MS Office from the Control Panel (basically reloads MS
Office).
4. Searched all Microsoft support and knowledge base locations I could
find pertinent to Access 2007.
5. Searched the Access World Forums
(http://www.access-programmers.co.uk/forums/) for pertinent info.

These actions produce no results.

If anyone has any info about these issues, please advise.
If not, what is the best way to "report" these issues to Microsoft so I
can see if Microsoft has any insight into what is happening?

Thanks for any assistance.

Dave

 

[Dave]

Thank you for the extensive response. I'll try these steps tomorrow and
post results.

Dave

 

[Dave]

Allen,

I tried all of your suggestions (twice), with no luck.

Do you think it would help to create a new blank database and import the
objects one at a time to see if I can identify the corrupted object? Or, is
that a waste of time?

Thanks again for your help.

Dave

---------------

 

[Allen Browne]

If the decompile did not work, then yes: importing into a new database would
be a good idea.

Make sure you turn Name AutoCorrect off in the new database before import.

You can import corruption, so that's why the decompile is important.

If you know which form is corrupted, the undocumented
SaveAsText/LoadFromText sometimes helps.

 

[Paul Shapiro]

In addition to Allen's suggestions, you can save time by importing objects
in batches. If what you've imported is uncorrupted, save a copy and then try
importing the next batch. It's usually a lot quicker than one at a time. I
usually do all the tables first, and then maybe all the queries, then the
code modules, etc. Once you hit the corruption, go in smaller chunks.

 

[Dave]

Thanks for the suggestion. Will do ....

Dave

------------------

 

[Tony Toews [MVP]]

In addition to Allen's suggestions, you can save time by importing objects
in batches. If what you've imported is uncorrupted, save a copy and then try
importing the next batch. It's usually a lot quicker than one at a time. I
usually do all the tables first, and then maybe all the queries, then the
code modules, etc. Once you hit the corruption, go in smaller chunks.

Agreed. I import all the tables, then the queries, then the forms and
so forth. But once Access crashes then I look in the new MDB and
that will tell me the last object that successfully imported. So now
which object (or objects) were causing me problems.

Also if you have a lot of objects minimize the database container
window then do the import. The import will go much faster as Access
doesn't have to waste more and more time redisplaying the database
container window. If you're only dealing with 50 or 100 query, form
or report objects then this isn't a big deal. Five hundred or a
thousand then this gets important.

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/

 

[Dave]

Thanks for the advice. There are about 125 objects in the database (tables,
queries, forms, reports & modules), so it should not take too long. I'll
let everyone know how it turns out.

Dave

 

[Dave]

FYI -- All my attempts to "fix the database" resulted in no change. I tried
everything everyone suggested multiple times, with negative results.

I even uninstalled and installed Access and the issues remain.

BUT, when I took the database to another computer with Access 2007,
everything worked fine!!!!

This leads me to believe there is something in my Access "configuration"
that is a problem. Which leads me to this question: How can I COMPLETELY
remove Access 2007 from my computer (program, configuration files, registry
entries, add-ins, etc.) so I can get a clean install?

Any advice will be greatly appreciated.

Dave

 

[Jan de Wit]

Dave, consider downloading Revouninstaller from
http://www.revouninstaller.com/. This little freeware program removes
installed programs much better than Microsoft.
On top of that, try
http://www.iobit.com/advancedwindowscareper.html?Str=download . Another
freeware program, that completely cleans out all obsolete registry files.

 

[Dave]

Thanks for the advice. Will do.

Dave