Access bombs

[MarianneZ]

I am developing an application in Access 2007. I have created a report. When
I bring up this report in Design View and go to look at the Vba code, Access
bombs. This happens if I click on the tool in the upper right of the Report
Design toolbar and if I click on the [...] in the Property list. Now I'm a
newbie and my code may well be imperfect, but it shouldn't cause Access to
bomb. I didn't have this problem earlier today, but I did yesterday. I
managed to recover from yesterday's problem by jettisoning an intermediate
version of the form.

This is very discouraging.

 

[MarianneZ]

Just a thought. Is there a limit to how big - long- Vba code 'pieces' can be?

 

[Tom van Stiphout]

On Wed, 10 Dec 2008 19:16:06 -0800, MarianneZ

Not really. What you are seeing is not normal. You may want to import
all your objects into a new database.

-Tom.
Microsoft Access MVP

Just a thought. Is there a limit to how big - long- Vba code 'pieces' can be?

I am developing an application in Access 2007. I have created a report. When
I bring up this report in Design View and go to look at the Vba code, Access
bombs. This happens if I click on the tool in the upper right of the Report
Design toolbar and if I click on the [...] in the Property list. Now I'm a
newbie and my code may well be imperfect, but it shouldn't cause Access to
bomb. I didn't have this problem earlier today, but I did yesterday. I
managed to recover from yesterday's problem by jettisoning an intermediate
version of the form.

This is very discouraging.

 

[ads]

I would agree with importing the forms / tables etc into a new
database, however you can also run "decompile" on an access database
too,

When you do compiles in access it doesn't remove previous compilations
of the code, if there is a corruption in the previous compilations,
the form maybe referring back to it.

try a decompile, then start the application normally and try to get to
the VBA code again.

Cheers

On Wed, 10 Dec 2008 19:16:06 -0800, MarianneZ


Not really. What you are seeing is not normal. You may want to import
all your objects into a new database.

-Tom.
Microsoft Access MVP

Just a thought. Is there a limit to how big - long- Vba code  'pieces'can be?

I am developing an application in Access 2007. I have created a report.. When
I bring up this report in Design View and go to look at the Vba code, Access
bombs. This happens if I click on the tool in the upper right of the Report
Design toolbar and if I click on the [...] in the Property list. Now I'm a
newbie and my code may well be imperfect, but it shouldn't cause Access to
bomb. I didn't have this problem earlier today, but I did yesterday. I
managed to recover from yesterday's problem by jettisoning an intermediate
version of the form.
This is very discouraging.

 

[Eduardo Aguilar Stange]

Den 08-12-11 04.16, i artikeln
(e-mail address removed), skrev "MarianneZ"

Just a thought. Is there a limit to how big - long- Vba code 'pieces' can be?

I am developing an application in Access 2007. I have created a report. When
I bring up this report in Design View and go to look at the Vba code, Access
bombs. This happens if I click on the tool in the upper right of the Report
Design toolbar and if I click on the [...] in the Property list. Now I'm a
newbie and my code may well be imperfect, but it shouldn't cause Access to
bomb. I didn't have this problem earlier today, but I did yesterday. I
managed to recover from yesterday's problem by jettisoning an intermediate
version of the form.

This is very discouraging.

 

[MarianneZ]

Thanks to all. The decompile worked.

Den 08-12-11 04.16, i artikeln
(e-mail address removed), skrev "MarianneZ"

Just a thought. Is there a limit to how big - long- Vba code 'pieces' can be?

I am developing an application in Access 2007. I have created a report. When
I bring up this report in Design View and go to look at the Vba code, Access
bombs. This happens if I click on the tool in the upper right of the Report
Design toolbar and if I click on the [...] in the Property list. Now I'm a
newbie and my code may well be imperfect, but it shouldn't cause Access to
bomb. I didn't have this problem earlier today, but I did yesterday. I
managed to recover from yesterday's problem by jettisoning an intermediate
version of the form.

This is very discouraging.