Is there a back door into the VBA Code? The usual way no longer w

  • Thread starter Thread starter Jules Bartow
  • Start date Start date
J

Jules Bartow

Something in Access 2007 VBA code/interface is corrupted with no apparent
reason or recovery.

I can edit and run all of my tables, queries, and pass-through queries,
forms, and reports --no problem there, until I try to run some code by
clicking on some buttons, list objects, and Treeview.

When I try to look at the Visual Basic code either through (Database Tools
tab | Visual Basic) or from within Design View via (Right-click object |
Build Event | Code Builder) or clicking on the Visual Basic icon in the
upper right corner I get:

"Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the inconvenience."

The VB code for some object events works fine while for other objects Access
returns the same error. The macro builder works fine. I'm not running
encryption. The only ActiveX object is the Treeview --which was working
great up until this anomaly.

The debugger responds with:

09BF8C65 mov ebx,dword ptr [eax+0Ch]

Unhandled exception at 0x09bf8c65 in MSACCESS.EXE: 0xC0000005: Access
violation reading location 0x0000000c.

VBE6.DLL!09bf8c65()
[Frames below may be incorrect and/or missing, no symbols loaded for
VBE6.DLL]VBE6.DLL!09bf8d0f()
VBE6.DLL!09b94e2a()
VBE6.DLL!09b93a80()
VBE6.DLL!09ac7db5()
VBE6.DLL!09a9235f()
sxs.dll!7e721487()
sxs.dll!7e7ae346()
user32.dll!7e4292e3()
imm32.dll!76399b35()
imm32.dll!76392b56()
user32.dll!7e46b90e()
user32.dll!7e4304bd()

How do I fix my code? There's a couple days worth of elegant (IMHO) code I
don't want to lose since the last backup.
 
Have you tried importing the modules into a new db? I've never heard of an
error like this, and you might get the same thing trying to import into a new
db, but it might be worth a shot if you haven't tried already.

--
Jack Leach
www.tristatemachine.com

- "Success is the ability to go from one failure to another with no loss of
enthusiasm." - Sir Winston Churchill
 
Jack,

I tried all kinds of things including your suggestion. I just came up with
the solution based on another post, which seemed similar. The answer, my
friend, is not blowin' in the wind as Bob Dylan suggested and I feared. It's
decompile.

Click Start | Click Run | Enter
"C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE" /decompile
"C:\Documents and Settings\Jules Bartow\My Documents\Projects.accdb"
| Click OK

Voilà! I can see my code again. Thank God / Bill Gates for this forum and
everyone else for taking the time to share their knowledge.


dymondjack said:
Have you tried importing the modules into a new db? I've never heard of an
error like this, and you might get the same thing trying to import into a new
db, but it might be worth a shot if you haven't tried already.

--
Jack Leach
www.tristatemachine.com

- "Success is the ability to go from one failure to another with no loss of
enthusiasm." - Sir Winston Churchill


Jules Bartow said:
Something in Access 2007 VBA code/interface is corrupted with no apparent
reason or recovery.

I can edit and run all of my tables, queries, and pass-through queries,
forms, and reports --no problem there, until I try to run some code by
clicking on some buttons, list objects, and Treeview.

When I try to look at the Visual Basic code either through (Database Tools
tab | Visual Basic) or from within Design View via (Right-click object |
Build Event | Code Builder) or clicking on the Visual Basic icon in the
upper right corner I get:

"Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the inconvenience."

The VB code for some object events works fine while for other objects Access
returns the same error. The macro builder works fine. I'm not running
encryption. The only ActiveX object is the Treeview --which was working
great up until this anomaly.

The debugger responds with:

09BF8C65 mov ebx,dword ptr [eax+0Ch]

Unhandled exception at 0x09bf8c65 in MSACCESS.EXE: 0xC0000005: Access
violation reading location 0x0000000c.

VBE6.DLL!09bf8c65()
[Frames below may be incorrect and/or missing, no symbols loaded for
VBE6.DLL]VBE6.DLL!09bf8d0f()
VBE6.DLL!09b94e2a()
VBE6.DLL!09b93a80()
VBE6.DLL!09ac7db5()
VBE6.DLL!09a9235f()
sxs.dll!7e721487()
sxs.dll!7e7ae346()
user32.dll!7e4292e3()
imm32.dll!76399b35()
imm32.dll!76392b56()
user32.dll!7e46b90e()
user32.dll!7e4304bd()

How do I fix my code? There's a couple days worth of elegant (IMHO) code I
don't want to lose since the last backup.
Click to expand...
Click to expand...
 
aahh... of course, decompile. That one didn't jump in my head right away.

Glad you got it figured out anyway... lotsa backups from now on right? <g>
--
Jack Leach
www.tristatemachine.com

- "Success is the ability to go from one failure to another with no loss of
enthusiasm." - Sir Winston Churchill


Jules Bartow said:
Jack,

I tried all kinds of things including your suggestion. I just came up with
the solution based on another post, which seemed similar. The answer, my
friend, is not blowin' in the wind as Bob Dylan suggested and I feared. It's
decompile.

Click Start | Click Run | Enter
"C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE" /decompile
"C:\Documents and Settings\Jules Bartow\My Documents\Projects.accdb"
| Click OK

Voilà! I can see my code again. Thank God / Bill Gates for this forum and
everyone else for taking the time to share their knowledge.


dymondjack said:
Have you tried importing the modules into a new db? I've never heard of an
error like this, and you might get the same thing trying to import into a new
db, but it might be worth a shot if you haven't tried already.

--
Jack Leach
www.tristatemachine.com

- "Success is the ability to go from one failure to another with no loss of
enthusiasm." - Sir Winston Churchill


Jules Bartow said:
Something in Access 2007 VBA code/interface is corrupted with no apparent
reason or recovery.

I can edit and run all of my tables, queries, and pass-through queries,
forms, and reports --no problem there, until I try to run some code by
clicking on some buttons, list objects, and Treeview.

When I try to look at the Visual Basic code either through (Database Tools
tab | Visual Basic) or from within Design View via (Right-click object |
Build Event | Code Builder) or clicking on the Visual Basic icon in the
upper right corner I get:

"Microsoft Office Access has encountered a problem and needs to close. We
are sorry for the inconvenience."

The VB code for some object events works fine while for other objects Access
returns the same error. The macro builder works fine. I'm not running
encryption. The only ActiveX object is the Treeview --which was working
great up until this anomaly.

The debugger responds with:

09BF8C65 mov ebx,dword ptr [eax+0Ch]

Unhandled exception at 0x09bf8c65 in MSACCESS.EXE: 0xC0000005: Access
violation reading location 0x0000000c.

VBE6.DLL!09bf8c65()
[Frames below may be incorrect and/or missing, no symbols loaded for
VBE6.DLL]VBE6.DLL!09bf8d0f()
VBE6.DLL!09b94e2a()
VBE6.DLL!09b93a80()
VBE6.DLL!09ac7db5()
VBE6.DLL!09a9235f()
sxs.dll!7e721487()
sxs.dll!7e7ae346()
user32.dll!7e4292e3()
imm32.dll!76399b35()
imm32.dll!76392b56()
user32.dll!7e46b90e()
user32.dll!7e4304bd()

How do I fix my code? There's a couple days worth of elegant (IMHO) code I
don't want to lose since the last backup.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top