Topics Search

DB Crashes on open of VBA

DB Crashes on open of VBA
Views: 95
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:

Similar posts...

 

Access 2010 SP1 – Random crashes in certain database or when opening the VBA

Access 2010 SP1 – Random crashes in certain database or when opening the VBA Icon
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
 

Opening tables for important database

Opening tables for important database Icon
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

Execute Excel Macro from Access failing Icon
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

Checking if a document of the same name is already open prior to trying to save it again Icon
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?
 

Make VB Project forget open code documents

Make VB Project forget open code documents Icon
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.).
 

App crashes whenever opned a form that had VBA

App crashes whenever opned a form that had VBA Icon
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

Access Database causing crash error VBE7.dll Icon
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.
 

VBA to open all linked tables

VBA to open all linked tables Icon
Correct me if I'm wrong but it seems as if queries take less time to run if the LINKED tables they are using are open in the database prior to trigging the run command. This is something I read on line. is this true?

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 ()?
 

Access 2010 - SP1 and October 2011 Patch

Access 2010 - SP1 and October 2011 Patch Icon
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.
 

Can't delete object - MSAccess crashes

Can't delete object - MSAccess crashes Icon
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.