DB Crashes on open of VBA

I have a DB that worked fine yesterday. I came in this AM and it crashes every time I try to open any module or VBA code. I have tried Compact & Repair as well as migrating to a new shell DB.

This is pretty crucial and I am at a loss as to where to begin debugging. It's not when I'm running anything. Strictly when I try to open modules/code for developing.

Sponsored Links:

Related Topics

Access 2010 SP1 – Random crashes in certain database or when opening the VBA
After installing Office 2010 SP1, you may receive random crashes when opening objects in certain databases and when trying to open the VBA window in those databases. If you look in theevent viewer the crash info may look similar to the following:

Faulting application: msaccess.exe
Version: 14.0.6024.1000
Stamp: 4d83e4fc
faulting module: vbe7.dll
version: 7.0.16.19
stamp: 4d430aec


Access crashes when editing VBA
I can start Access and VBA module without problems. But when I edit VBA (first keystroke) Access VBA plugin freezes and crashes.

Problem is on all databases using VBA
If I log on as a other user, problem isn't there.
I use Win7 64bit, Access 2010 32bit
I use .mdb format only
I've tried access.exe mydatabase.mdb /decompile

I would log on as other user, rename c:\users\myprofile and thus force it to create a new profile for me. But Windows 7 just creates a temporary profile as it can't find the old one.
I would prefer not to delete my profile through control panel, as I would like to be able to undo the change


Compact and Repair crashes on larger databases
When I try to run compact and repair on any database that is ~500MB or larger, Access crashes . It is pretty consistent on when it crashes. e.g. a DB that is 692MB crashes when the temp DB reaches 569MB.

Here is where it gets stranger. .problem happens on multiple databases and I can copy the DB to another computer with Access 2007 (Same version) and Compact/Repair works fine.

For problem / attempted corrections I have tried the following with no luck

Checkdsk - OK
Boot in Save Mode - Compact / Repair still crashes
Move DB to another HD on my computer (Thinking I may have disk failing) - Compact / Repair still crashes
Uninstall / Install Access - - Compact / Repair still crashes


Command button click crashes access 2007 unless VBA editor is open
I have a form with 2 buttons. One button is an "exit" button with no customization. The other button is a "search" button that runs a bit of code. Until recently, everything worked fine.

I think they only thing I've changed in my db is that I selected "compact on close."

Now every time I click the "exit" button, it still works fine. When I click the "search" button access crashes. If I open the vba editor and then click "search," it works fine.

I'm not sure where to go with this one


Access crashes when editing VBA
I can start Access and VBA module without problems.
But when I edit VBA (first keystroke) Access VBA plugin freezes and crashes.

Problem is on all databases using VBA
If I log on as a other user, problem isn't there.
I use Win7 64bit, Access 2010 32bit
I use .mdb format only
I've tried access.exe mydatabase.mdb /decompile

I would log on as other user, rename c:\users\myprofile and thus force it to create a new profile for me. But Windows 7 just creates a temporary profile as it can't find the old one.
I would prefer not to delete my profile through control panel, as I would like to be able to undo the change

EDIT: Actually, this might not be an VBA issue - I found out that I have no problems editing VBA code that has no forms (GUI), so the problem just might be regarding Forms and not VBA


access crashing
me. I'm running Access 2010 on Windows 7, and it crashes all the time. Most recently I created a database with 5 tables, 4 of which are used as look-up tables for data in the 5th table. I entered all the necessary records in the 4 tables, then entered about 20 records in Table 5, then closed the file for a few hours. Now, when I open it, one of the look-up tables will not open and if I click to open it, Access crashes. Is this normal?

I'm about to give up on my version of Access and throw it through a 10th story window


Opening tables for important database
Somewhere I vaguely remember reading about using VBA to open my tables for an ACCESS and manage all of the datasets with VBA so to control record locking and preventing problems. It is easier to let ACCESS do it by following the wizards but this project is going to be important for my career.

I can't remember where I read this, or even if it is true. but if 100+ users over start to use this DB and it crashes - then I'm toast!

Should I rely on VBA and record lock and prevent crashesby code OR use ACCESS built in Forms, Tables?


Execute Excel Macro from Access failing
I am trying to run the code below in my access 2007 database to start an excel macro. However, I need to make some changes to it that far exceed my applicable knowledge. The changes are below:

1. The macro currently only runs correctly when Excel is not running and the Personal.XLSB workbook is closed. I need theo macro to be smart enough to open Personal.xlsb if needed, or runthe code if it is already open.

2. The Macro that is built in Excel VBA opens several workbooks makes changes to them, then closes some and leaves some open and send a couple of emails. The Access VBA closes excelcompletely and crashes if I try to remove this line

xlsApp.Quit

How do I keep the Access VBA from closing excel?

3. I currently have the path hardcoded to my personal.xlsb, however I need this to be able to run from any one of my colleagues computers so I would like the path to the personal.xlsb workbook be relative.


Checking if a document of the same name is already open prior to trying to save it again
I am trying to write VBA functions to act as error handlers for a database.

The database form allows you to select certain fields and by clicking a button it automatically generates a word document for the user, opens the document for viewing and saves as a file name in a predetermined folder.

The problem I am having is that if the user selects the generate report button twice without closing the word document first it crashes due to the document being already open.

Is there a way to check to see if the document is open before it tries to generate the report again and alert the user that the document is already open?


Access 2003 crashes on Quit
I want my reports to close on deactivation. So if have in Access2003:
Private Sub Report_Deactivate()
Docmd.Close
End Sub

This works fine if the report loses focus, is minimized or is closed.

But if the report is open and Access is terminated, then access crashes. The crash occurs AFTER the event! This solution worked perfect in Access 2000.


Make VB Project forget open code documents
My Visual studio crashes every time I open a specific project, because before closing VS2010 last, I forgot to close a .vb file that I had drug to my second monitor. The issue is likely related to floating tab wells in the VS Productivity Power Tools extension.

now when I try to load the solution it will progress part way, but when it tries to reopen the documents thathad previously been open, it crashes hard.

anyway, I am trying to find out where VS stores info about the code documents that were open at last project close, so I can clear it out.

does anyone know where VS stores info about the previously opened code documents? I've checked the project and solution files but neither appears to hold this info. I know that the locationmust be within the project however, since getting a new version of the codebase from source control corrects the issue (but I still have code to check in.).


Stability of DB
I've created a DB in Access2010. After doing an extensive amount of work, frequently when I open the DB, Access crashes. The message states Microsoft Access has stopped working. When I click on the view problem details, it gives a lot of information, but nothing that I'm able to intrepret. I've tried creating a new DB, and importing the objects, and it also crashes during the import. Has anyone experienced a problem like this? My machine is operating properly, and as of this writing, I'm only experiencing this problem within this DB


Can't delete object - MSAccess crashes
I was working on a datablase for a few weeks and all was well. I then decided to import a Form from another database to adapt and use. But now Access keeps crashing everytime I try and open that imported Form.

I can only go into it in Design View but when I try to delete the form to get rid of it, Access crashes.

Trouble is I can't keep that form because now I can't go into VB as it crasshes then too.

The database the form came from works absolutely fine and I've used it for years.


DoCmd.SendObject crashes 2007
I have a button which opens a new email message with a report attached. This works fine when I have Outlook open already. However, if outlook is not open, Access crashes.

What I have read so far is that you will need SP2 of runtime. At this time it is not feasible to upgrade of the users computers to SP2 (as the program it is in will be used on different computers).

I was wondering if there is code to open Outlook before opening the new message or if there was a better solution to accomplish this.

DoCmd.SendObject acSendReport, "Lost Item Report", acFormatPDF, txtEmail.Value, "", "", "Your Lost Item Report", "" & vbNewLine & "Report Filed: " & txtRptDate.Value & vbNewLine & "Method: " & cboRptMethod.Text, True


access database crashes ...
I have Microsoft Office 2010 32 bit installed on Microsoft Windows 7 Prof 64 bit the database is accdb. Recently (one week or so ) I have started experiencing database corruption error: I cannot open any form , report or vba module, tables are still accessible though ,most of the linked anyway to SQLDB. So I had to create back up every one hour otherwise I have to redo all the work all other again. I have tried to create the new empty file and import everything from the backup and apply all the changes but after one day or so it is happening again! So it goes like that: I restore it from the backup, apply changes , all good, but as soon as I close it to create another back up and open again it already corrupted.


VBA Crashes Access
I couldn't figure out why one of my Access 2010 applications crashed whenever you opened a form that had VBA code tied to it or even just opened the Visual Basic Editor.

I tried a lot of things and ultimately found out that I had a corrupt icon that was "used" in the File-Options-Current Database-Application Icon. When I removed and/or replaced the icon, VBA didn't crash anymore.


Access Database causing crash error VBE7.dll
I have an access database that seems to be crashing for no reason. The only thing I can thin is that something is going on with a VBA module I was working on. Long story short it doesn't happen with other files but anytime I load of this database within a minute or so it just crashes.

I can cause an instant crash by entering text into a form which is tied to some VBA script.

It doesn't give an error it just dies and the windows "you program broke" message comes up. after checking the event viewer I found the following

Error | 7/12/2011 8:28:47 AM | Application Error | 1000 | (100) Faulting application name: MSACCESS.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e4fc
Faulting module name: VBE7.DLL, version: 7.0.16.19, time stamp: 0x4d430aec Exception code: 0xc0000005
Fault offset: 0x00120b7a
Faulting process id: 0xa8c
Faulting application start time: 0x01cc408f2020703d
Faulting application path: C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE
Faulting module path: C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL Report Id: 7d1c2df2-ac82-11e0-ae07-bc305ba6eb47

I have tried a repair on the database through access but access crashes every time. I also did a repair on Office to be sure it wasn't an issue with Access itself.

Also it crashes anytime I try to go into the VBA script editor.


database crashes
all. I changed a control on my form to a combobox when I try the view the form it crashes! I get that error where the database has encountered a problem and must close! what's going on please


docmd.transferspreadsheet crashes access
I am having some trouble with the docmd.transferspreadsheet function, everytime I run it, it crashes Access. I have used the docmd.outputto function and that works fine but I need the queries to be in the same excel file but in different sheet and the docmd.outputto open a new excel file for each query.

[CODE]

I have tried to display an error message but Access just freezes and I get the program not responding message |


Access 2010 - SP1 and October 2011 Patch
Once the fix is available sometime this month in the October Cumulative update, the KB article will be updated with information about the patch including where to download it from, how to install it, and prerequisites to the install.

2625046 Access 2010 crashes in VBE7.DLL after installing Office 2010 SP1 [LINK]

After spending the morning reading the Microsoft Answers site titled: "Access 2010 SP1 - You receive random crashes in certain database or when opening the VBA window in those databases after installing Office 2010 SP1"

It appears that MS Office 2011 including MS Access has a problem with the new versoin of VBA. It is described by coders as catastrophic. Replace 'random" with constant. Also add code erased.

when, where and results if anyone else is involved in Access 2010 SP1.