Unhandled win32 exception occurred in MSACCESS.EXE [6648]

[AccessCorruption]

Hello,



I'm a web developer who's taken over an ADP project and needs help with the Windows and Access Environments.

I was coding in VBA in Access 2007, and would at times need to rebuild the project by importing forms, reports, and modules due to corruption issues. I believe these issues were caused by run-time errors during coding.

I've upgraded to Access 2010 (Office Suite 2010 32-bit) on a Windows 7 Machine (64-bit). The same (I believe) corruption issues in Access 2010 are invoking the following error:

After making changes in my project, I will save, exit, and attempt to open the project. Access 2010 displays a message box "Access has stopped working". I click "debug" and Windows attempts to open the Visual Studio Just-In-Time debugger, with the following: "An unhandled win32 exception occurred in MSACCCESS.EXE [6648]"

I exit out of Access 2010 and attempt to reopen the file and it throws the same exception. I exit out again and attempt to open Access 2010 by itself, and Access attempts to create a Backup copy of the same file. The process fails and throws the same exception. I can open Access by holding the shift key while double-clicking, but when I attempt to rebuild the corrupted version I get the same error message as above. So my rebuild is failing, and I'm stuck in 2010. I can rebuild in 2007, but would like to fix this on this brand new machine which would be sweet to develop on.

Thanks for any help any one can provide me,

AccessCorruption

[ajetrumpet]

the answer you got here: http://stackoverflow.com/questions/8...-msacccess-exe

is probably more than you'll get at this forum. Stackoverflow is home to some brilliant people. Nothing against this forum, but you'll probably have better luck over there, especially with windows issues.

But apparently you guys know how to automate cross posting anyway. Or have the appropriate tools. So I'm sure you know that by now.

[AccessCorruption]

Thanks for your advice on Stack Overflow. I want to make clear that there is no automated software being used to cross-post. I have a serious issue, I selected two mediums, here and Stack Overflow because I want to reach more people with potentially different skill sets. The issue has not yet been fully resolved, and I would appreciate input from anyone who would be willing to share their views. Thanks.

[ajetrumpet]

Thanks for your advice on Stack Overflow. I want to make clear that there is no automated software being used to cross-post. I have a serious issue, I selected two mediums, here and Stack Overflow because I want to reach more people with potentially different skill sets. The issue has not yet been fully resolved, and I would appreciate input from anyone who would be willing to share their views. Thanks.

the bottom line here could simply be that Access is a piece of junk. Literally, that is very true. MS office products are not well made, nor have they ever been, and Access is one of the worst MS distributes.

As you've seen at Stack Overflow, the common accepted solution for assumed corruption issues is to either A) import all objects to a new file, or B) decompile the project and compile it again.

Personally, I think those methods are accepted because there's literally nothing else you can do. You can of course, trace your steps back in time to pinpoint the exact moment the corruption error first started to happen. That method should allow you to target the small amount of changes to your OS/machine that could have brought the problem about.

Other than that, I doubt you can do anything really. Although, searching the error reveals this:

This guy re-installed his office and solved the issue: http://www.boards.ie/vbulletin/showt...php?p=54776061

For instance, if this is a windows issue that is somehow related to Access's operation, uninstalling the problem might fix it. And I suppose the lesson to be learned by that thread is that...sometimes on windows OS platforms, MS software just completely sucks and if you want real reasons as to why illegitimate corruption happens, you'll have to research the software's execution yourself. Otherwise, the simplest solution might be the one that fixes things.

more useful info: http://www.sikhphilosophy.net/17056-post2.html

more info about unhandled exceptions: http://support.microsoft.com/kb/826220

That article, and many others, mentions certain controls. Be aware that 2010's operation is much different than it's predecessors. For instance, macro structuring is different, and old files must be opened in order to work with the new 2010 operations and read of the macros. So you see, the variables that cause the issue here are endless.

[AccessCorruption]

Thank you for your time. I uninstalled and re-installed Office 2010, but the problem persists. Holding the shift key while opening Access, holding the shift key while opening the file, canceling the backup attempt each time it fires, and using this method below at least allows me to continue to work. For now, almost every time I get a run-time error Access bombs and I'll need to re-open the project. I'm going to clear out any deprecated 2007 features and try to implement a error handler class module for all objects.

http://rogersaccessblog.blogspot.com...-database.html