Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Access 2010 Crashes When Opening Code
767 views
Skip to first unread message
Gilgamesh
Oct 31, 2011, 12:58:50 PM10/31/11
to
Hi,
I'm not sure my 'Subject' above summarizes the problem well.
The database was originally an Access 2003 database (.mdb), but I
converted it to MS Access 2010 and I have been working on it for
several months without any problems.
It had tables, queries (selects and make table and append types), and
reports but no forms and no explicitly written Visual Basic.
A week or so ago I added a form with a few buttons. I wrote some VBA
for the event procedures for the buttons and the open form event. It
was all working just great. I could run the form and click the
buttons. I could step into the code if I wanted. I temporarily
dropped tables to ensure that my error handling was working. All was
good. I closed everything on Friday evening and went home. Today,
Monday, there is a big problem.
I can run reports and queries. If I open a table the data are all
there. But, if I try to do anything with the code, such as open the
form, or click on the event procedure in the properties window of a
button, or click "View Code" when the form is open in Design View, or
try to add a new button when the form is in design view, Access
crashes. All I can do is tell it to close the program and everything
goes away, leaving the .accdb file and the lock.
The dialog that comes up says "Microsoft Access has stopped working.
Windows can check online ... " It gives me the option to check online
and restart or just restart. The check online option causes Access to
crash completely; restart does restart access but does not fix
anything..
Access is installed on my C drive and the database file is on my C
drive too.
These are the problem details one sees trying to open the form or view
the code or add a new button:
Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 14.0.6024.1000
Application Timestamp: 4d83e4fc
Fault Module Name: VBE7.DLL
Fault Module Version: 7.0.16.19
Fault Module Timestamp: 4d430aec
Exception Code: c0000005
Exception Offset: 00020418
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional information about the problem:
LCID: 1033
skulcid: 1033
Anyone have any ideas? Help.
Mike
I'm not sure my 'Subject' above summarizes the problem well.
The database was originally an Access 2003 database (.mdb), but I
converted it to MS Access 2010 and I have been working on it for
several months without any problems.
It had tables, queries (selects and make table and append types), and
reports but no forms and no explicitly written Visual Basic.
A week or so ago I added a form with a few buttons. I wrote some VBA
for the event procedures for the buttons and the open form event. It
was all working just great. I could run the form and click the
buttons. I could step into the code if I wanted. I temporarily
dropped tables to ensure that my error handling was working. All was
good. I closed everything on Friday evening and went home. Today,
Monday, there is a big problem.
I can run reports and queries. If I open a table the data are all
there. But, if I try to do anything with the code, such as open the
form, or click on the event procedure in the properties window of a
button, or click "View Code" when the form is open in Design View, or
try to add a new button when the form is in design view, Access
crashes. All I can do is tell it to close the program and everything
goes away, leaving the .accdb file and the lock.
The dialog that comes up says "Microsoft Access has stopped working.
Windows can check online ... " It gives me the option to check online
and restart or just restart. The check online option causes Access to
crash completely; restart does restart access but does not fix
anything..
Access is installed on my C drive and the database file is on my C
drive too.
These are the problem details one sees trying to open the form or view
the code or add a new button:
Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 14.0.6024.1000
Application Timestamp: 4d83e4fc
Fault Module Name: VBE7.DLL
Fault Module Version: 7.0.16.19
Fault Module Timestamp: 4d430aec
Exception Code: c0000005
Exception Offset: 00020418
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional information about the problem:
LCID: 1033
skulcid: 1033
Anyone have any ideas? Help.
Mike
Gilgamesh
Oct 31, 2011, 1:07:55 PM10/31/11
to
I clicked the Restart option presetned when the error occurs, the
backup is just fine. The code is there and everything works. Sorry
to bother you all.
Mike
Patrick Finucane
Oct 31, 2011, 2:24:07 PM10/31/11
to
acknowleging the problem somewhere on the internet. Anyway, the
advice in the article was to run a /decompile on the file. I did so
and my code that was literally lost was available oncee again.
Bob Darlington
Oct 31, 2011, 6:48:30 PM10/31/11
to
"Gilgamesh" <michae...@gmail.com> wrote in message
news:bdd4df50-72a8-4f52...@h23g2000pra.googlegroups.com...
(during design only) than they ever did using 2002.
On each occasion, I find that decompile works, but there is obviously a
problem somewhere.
It is happening both on apps imported from 2002 format and those newly
developed in 2010.
--
Bob Darlington
Brisbane
Tony Toews
Nov 1, 2011, 12:56:05 AM11/1/11
to
On Mon, 31 Oct 2011 09:58:50 -0700 (PDT), Gilgamesh
<michae...@gmail.com> wrote:
Just to follow up
Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
start-up times
http://www.granite.ab.ca/access/decompile.htm
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
<michae...@gmail.com> wrote:
Just to follow up
Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
start-up times
http://www.granite.ab.ca/access/decompile.htm
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Gilgamesh
Nov 1, 2011, 12:35:29 PM11/1/11
to
On Oct 31, 9:56 pm, Tony Toews <tto...@telusplanet.net> wrote:
> On Mon, 31 Oct 2011 09:58:50 -0700 (PDT), Gilgamesh
>
> On Mon, 31 Oct 2011 09:58:50 -0700 (PDT), Gilgamesh
>
> <michaelsfl...@gmail.com> wrote:
>
> Just to follow up
>
> Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
> start-up timeshttp://www.granite.ab.ca/access/decompile.htm
>
> Just to follow up
>
> Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
> For a convenient utility to keep your users FEs and other files
> updated seehttp://www.autofeupdater.com/
Thank you Bob, Patrick, and Tony.
> updated seehttp://www.autofeupdater.com/
Phil
Nov 1, 2011, 2:39:53 PM11/1/11
to
Phil
Tony Toews
Nov 1, 2011, 3:24:09 PM11/1/11
to
On Mon, 31 Oct 2011 09:58:50 -0700 (PDT), Gilgamesh
<michae...@gmail.com> wrote:
> Fault Module Name: VBE7.DLL
From Armen Stein, fellow Access MVP
There is a hotfix now out for the Access 2010 SP1 problem that causes
VBA code to be corrupted, requiring frequent decompiles. The fix is
to VBE7.dll.
It is downloadable from:
http://support.microsoft.com/kb/2596585
It's a bit confusing, because the version detector assumes you'll want
the 64-bit version if you're running Windows 64-bit. I believe that
since most of us are running Office 32-bit, you'll need to manually
request the x86 version.
Tony
--
Tony Toews, Microsoft Access MVP
Jim Devenish
Nov 2, 2011, 1:05:25 PM11/2/11
to
On Nov 1, 7:24 pm, Tony Toews <tto...@telusplanet.net> wrote:
> On Mon, 31 Oct 2011 09:58:50 -0700 (PDT), Gilgamesh
>
> On Mon, 31 Oct 2011 09:58:50 -0700 (PDT), Gilgamesh
>
> <michaelsfl...@gmail.com> wrote:
> > Fault Module Name: VBE7.DLL
>
> From Armen Stein, fellow Access MVP
>
> There is a hotfix now out for the Access 2010 SP1 problem that causes
> VBA code to be corrupted, requiring frequent decompiles. The fix is
> to VBE7.dll.
>
> It is downloadable from:http://support.microsoft.com/kb/2596585
>
> It's a bit confusing, because the version detector assumes you'll want
> the 64-bit version if you're running Windows 64-bit. I believe that
> > Fault Module Name: VBE7.DLL
>
> From Armen Stein, fellow Access MVP
>
> There is a hotfix now out for the Access 2010 SP1 problem that causes
> VBA code to be corrupted, requiring frequent decompiles. The fix is
> to VBE7.dll.
>
> It is downloadable from:http://support.microsoft.com/kb/2596585
>
> It's a bit confusing, because the version detector assumes you'll want
> since most of us are running Office 32-bit, you'll need to manually
> request the x86 version.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
> request the x86 version.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
> For a convenient utility to keep your users FEs and other files
> updated seehttp://www.autofeupdater.com/
It's amazing that the version for Office 32 bit is x86. And not
> updated seehttp://www.autofeupdater.com/
something like x32 !!
How old terminology seems to hang around!
Tony Toews
Nov 2, 2011, 3:08:09 PM11/2/11
to
On Wed, 2 Nov 2011 10:05:25 -0700 (PDT), Jim Devenish
<internet...@foobox.com> wrote:
>> It's a bit confusing, because the version detector assumes you'll want
>> the 64-bit version if you're running Windows 64-bit. I believe that
<internet...@foobox.com> wrote:
>> It's a bit confusing, because the version detector assumes you'll want
>> since most of us are running Office 32-bit, you'll need to manually
>> request the x86 version.
>>
>> request the x86 version.
>>
>It's amazing that the version for Office 32 bit is x86. And not
>something like x32 !!
>
>How old terminology seems to hang around!
Good point. One of those things you take for granted. Now where's
>something like x32 !!
>
>How old terminology seems to hang around!
my PC XT?
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
0 new messages