DB Crashes on open of VBA
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.
Thank you for taking the time to report an issue.
What's wrong... Please write below.
Faulting application: msaccess.exe
faulting module: vbe7.dll
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?
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
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.
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?
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.).
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.
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: 184.108.40.206, 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.
also, with that said, what is the VBA to open all linked tables with in a database. should I have all databases open a form and have the form on open run the OpenAllLinkedTbls ()?
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.
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.