Corrupt forms that can’t be opened!

[MatBei]

Sometimes, when I try to save a form after I have been working in design mode
an error message appear. The error message says some thing like this “Can’t
save the form. Out off memoryâ€. Then, after closing the application without
saving changes, the form isn’t possible to open again and I have to redo the
work since the last back up.

Is this a known bug or lack of memory in my computer?

512 Mb RAM
Access 2003 SP3

 

[Chris O'C via AccessMonster.com]

While adding more RAM wouldn't hurt, you probably have a corrupt database
file. Create a new database file and import everything from the current
database into it, then compile the code and compact the database. See if
that helps.

Chris
Microsoft MVP

 

[Marshall Barton]

Sometimes, when I try to save a form after I have been working in design mode
an error message appear. The error message says some thing like this “Can’t
save the form. Out off memory”. Then, after closing the application without
saving changes, the form isn’t possible to open again and I have to redo the
work since the last back up.

Is this a known bug or lack of memory in my computer?

It is known, but not understood. The most common cause is
failing to switch a form back to design view before editing
its VBA module.

Decompile *might* be your friend. Some of the gory details
are at:
http://www.trigeminal.com/usenet/usenet004.asp?1033

 

[MatBei]

Thanks Chris,
I followed you suggested solution. All objects were successfully imported
into the new database except the corrupt one. I designed a new form to
replace it. Suddenly, the problem occurred again. Do you have any other
solutions!! The problem often occurs when I do some changed in a text
controls row source or the forms data source.

To prevent this I have to make back up copies every 10 minutes and it’s …


"Chris O'C via AccessMonster.com" skrev:

 

[Chris O'C via AccessMonster.com]

Use Marshall's recommendation, decompile. First make a copy of your file and
only work with the copy. Turn off any automatic startups: set the startup
form to none and rename your autoexec macro to something else temporarily.

Now use the /decompile switch in your startup command. I create windows
shortcuts for things like this. Here's an example of the shortcut's target.
(It should be all one line, but change it to match your paths and db name.)

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\database\db.
mdb" /decompile

Double click on the shortcut to decompile. When it's done, compile the code,
then compact/repair. Reset the startup form and autoexec macro to the way
they were. See if that helps.

Chris
Microsoft MVP

Thanks Chris,
I followed you suggested solution. All objects were successfully imported
into the new database except the corrupt one. I designed a new form to
replace it. Suddenly, the problem occurred again. Do you have any other
solutions!! The problem often occurs when I do some changed in a text
controls row source or the forms data source.

To prevent this I have to make back up copies every 10 minutes and it’s …

"Chris O'C via AccessMonster.com" skrev:

While adding more RAM wouldn't hurt, you probably have a corrupt database
file. Create a new database file and import everything from the current

[quoted text clipped - 14 lines]

 

[Alan]

Thanks Chris,
I followed you suggested solution. All objects were successfully imported
into the new database except thecorruptone. I designed a new form to
replace it. Suddenly, the problem occurred again. Do you have any other
solutions!! The problem often occurs when I do some changed in a text
controls row source or the forms data source.

To prevent this I have to make back up copies every 10 minutes and it’s …

"Chris O'C viaAccessMonster.com" skrev:





- Show quoted text -

Hi,

You may try Advanced Access Repair at http://www.datanumen.com/aar/
This tool is rather useful in salvaging damaged Access MDB files. Hope
this helps.

Alan