terpsichore
asked on
Access 2010 crashing - help
I have a front end file in Access 2010, with a separate data back-end. They have been working fine together.
I made a change to a single line of code (adding one more field to a sql string - setting the datasource for a continuous subform in a procedure) - and nothing else... the program crashes when i try to run it OR when I simply try to open up the Visual Basic code. It did this several times. This code isn't even in the form that is loading when the program loads.
I do not get a specific program error, but the generic "Microsoft Access has stopped running" and it hangs...
Before making the change, I have compacted and repaired both front and back-end.
Any ideas???
I made a change to a single line of code (adding one more field to a sql string - setting the datasource for a continuous subform in a procedure) - and nothing else... the program crashes when i try to run it OR when I simply try to open up the Visual Basic code. It did this several times. This code isn't even in the form that is loading when the program loads.
I do not get a specific program error, but the generic "Microsoft Access has stopped running" and it hangs...
Before making the change, I have compacted and repaired both front and back-end.
Any ideas???
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Reference to menu options in:
http://access.mvps.org/access/modules/mdl0039.htm
is broken.
You can use this registry patch (for Access 2010):
http://access.mvps.org/access/modules/mdl0039.htm
is broken.
You can use this registry patch (for Access 2010):
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.accdb]
@="Access.Application.14"
"Content Type"="application/msaccess"
[HKEY_CLASSES_ROOT\.mdb]
"Content Type"="application/x-msaccess"
@="Access.Application.14"
[HKEY_CLASSES_ROOT\Access.Application.14]
@="Microsoft Access Database"
[HKEY_CLASSES_ROOT\Access.Application.14\Shell\Decompile\command]
@="C:\\Program Files\\Microsoft Office\\Office14\\MSAccess.exe \"%1\" /DECOMPILE"
[HKEY_CLASSES_ROOT\Access.Application.14\Shell\Compact\command]
@="C:\\Program Files\\Microsoft Office\\Office14\\MSAccess.exe \"%1\" /COMPACT"
(correct path to MsAccess.exe, save this text as reg and run)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you install SP1? Many problems have been reported with VBA instability after SP1 is installed. You may want to try uninstalling it.
Apparently there is a fix scheduled this month:
http://answers.microsoft.com/en-us/office/forum/office_2010-access/access-2010-sp1-you-receive-random-crashes-in/d2bf6175-075a-4a12-a2b1-f55d40af271b
Apparently there is a fix scheduled this month:
http://answers.microsoft.com/en-us/office/forum/office_2010-access/access-2010-sp1-you-receive-random-crashes-in/d2bf6175-075a-4a12-a2b1-f55d40af271b
"Reference to menu options in:
http://access.mvps.org/access/modules/mdl0039.htm
is broken."
Works for me right now (10-8-2011 10:25 pdt). MVPS.org has been up/down lately ... not sure what's up.
"LSMConsulting:
Also, once you do the decompile option you should then Compile your VBA Code. To do that, open the VBA Editor and click Debug - Compile. Fix any code errors and continue doing this until that menu option is disabled."
That's included in the procedure I posted.
mx
http://access.mvps.org/access/modules/mdl0039.htm
is broken."
Works for me right now (10-8-2011 10:25 pdt). MVPS.org has been up/down lately ... not sure what's up.
"LSMConsulting:
Also, once you do the decompile option you should then Compile your VBA Code. To do that, open the VBA Editor and click Debug - Compile. Fix any code errors and continue doing this until that menu option is disabled."
That's included in the procedure I posted.
mx
<That's included in the procedure I posted.>
Sorry ... didn't see it in there.
Sorry ... didn't see it in there.
ASKER
Thanks to everyone; I'm still diagnosing this.
ASKER
I would like to have awarded more people - I was amazed by the smart and thoughtful responses. In the end, I upgraded my already reasonably current software, including BIOS, and the problem disappeared. I also learned an incredible amount from these posts. Thank you to all.
ASKER