By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,089 Members | 1,964 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,089 IT Pros & Developers. It's quick & easy.

Continual unrecoverable Form corruption

P: n/a
Hello,

I have a form that seems to corrupt over and over again. I can't open it in
design view, usually getting a message like "There isn't enough memory to
perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of controls
on the form; there are about 320 controls, but that is still about half of
the Access limit of 754. I also removed about 120 text boxes and placed
them in a subform to reduce the number of controls on the main form. Any
idea what might be causing this problem? at this point, I feel like I'm
spinning my wheels, because I have to keep restoring from a previous
version, then modify and hopefully save a copy before the form corrupts
again. One thing I should add, is the corruption only happens when I'm
modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick
Oct 15 '07 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Rico wrote:
Hello,

I have a form that seems to corrupt over and over again. I can't open it in
design view, usually getting a message like "There isn't enough memory to
perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of controls
on the form; there are about 320 controls, but that is still about half of
the Access limit of 754. I also removed about 120 text boxes and placed
them in a subform to reduce the number of controls on the main form. Any
idea what might be causing this problem? at this point, I feel like I'm
spinning my wheels, because I have to keep restoring from a previous
version, then modify and hopefully save a copy before the form corrupts
again. One thing I should add, is the corruption only happens when I'm
modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick


1)Try copying the form in the current database and try editing the copy.

2)Try importing the form into a clean database, that has any source
tables and queries defined.

3) Try saving the sub form and then replacing it with a very simple
subform - to see if that can be edited.

4) After recovering from a previous version, what edits do you do to the
form? After these edits are you EVER able to edit it?

Bob
Oct 15 '07 #2

P: n/a
remember that the 754 limit is life-span
it might be an idea to export the form (using application.saveastext) &
importing
(application.loadfromtext)
Pieter

"Rico" <me@you.comwrote in message news:BkPQi.14424$G25.2918@edtnps89...
Hello,

I have a form that seems to corrupt over and over again. I can't open it
in design view, usually getting a message like "There isn't enough memory
to perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of
controls on the form; there are about 320 controls, but that is still
about half of the Access limit of 754. I also removed about 120 text
boxes and placed them in a subform to reduce the number of controls on the
main form. Any idea what might be causing this problem? at this point, I
feel like I'm spinning my wheels, because I have to keep restoring from a
previous version, then modify and hopefully save a copy before the form
corrupts again. One thing I should add, is the corruption only happens
when I'm modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick


Oct 15 '07 #3

P: n/a
Rico wrote:
Hello,

I have a form that seems to corrupt over and over again. I can't open it in
design view, usually getting a message like "There isn't enough memory to
perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of controls
on the form; there are about 320 controls, but that is still about half of
the Access limit of 754. I also removed about 120 text boxes and placed
them in a subform to reduce the number of controls on the main form. Any
idea what might be causing this problem? at this point, I feel like I'm
spinning my wheels, because I have to keep restoring from a previous
version, then modify and hopefully save a copy before the form corrupts
again. One thing I should add, is the corruption only happens when I'm
modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick

Along with the other's comments...sometimes I open the "corrupt" form
and create a new form and select all controls on the bad form and do and
Edit/Copy from the bad form and Edit/Paste to the new form. Then copy
in the code. Then save the new form, delete the old.

Oct 15 '07 #4

P: n/a
That would work if I could open the form in design view. ;)
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
Rico wrote:
>Hello,

I have a form that seems to corrupt over and over again. I can't open it
in design view, usually getting a message like "There isn't enough memory
to perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of
controls on the form; there are about 320 controls, but that is still
about half of the Access limit of 754. I also removed about 120 text
boxes and placed them in a subform to reduce the number of controls on
the main form. Any idea what might be causing this problem? at this
point, I feel like I'm spinning my wheels, because I have to keep
restoring from a previous version, then modify and hopefully save a copy
before the form corrupts again. One thing I should add, is the
corruption only happens when I'm modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick

Along with the other's comments...sometimes I open the "corrupt" form and
create a new form and select all controls on the bad form and do and
Edit/Copy from the bad form and Edit/Paste to the new form. Then copy in
the code. Then save the new form, delete the old.

Oct 16 '07 #5

P: n/a
I tried SaveAsText but the app craps out before saving.

"Pieter Wijnen"
<it*********************************************** ***********@online.replace.with.norway>
wrote in message news:OZ**************@TK2MSFTNGP02.phx.gbl...
remember that the 754 limit is life-span
it might be an idea to export the form (using application.saveastext) &
importing
(application.loadfromtext)
Pieter

"Rico" <me@you.comwrote in message news:BkPQi.14424$G25.2918@edtnps89...
>Hello,

I have a form that seems to corrupt over and over again. I can't open it
in design view, usually getting a message like "There isn't enough memory
to perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of
controls on the form; there are about 320 controls, but that is still
about half of the Access limit of 754. I also removed about 120 text
boxes and placed them in a subform to reduce the number of controls on
the main form. Any idea what might be causing this problem? at this
point, I feel like I'm spinning my wheels, because I have to keep
restoring from a previous version, then modify and hopefully save a copy
before the form corrupts again. One thing I should add, is the
corruption only happens when I'm modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick



Oct 16 '07 #6

P: n/a
Hi Bob,

Thanks for your advice. I wound up recreating the entire form from scratch,
one control at a time, but, to answer your question;
4) After recovering from a previous version, what edits do you do to the
form? After these edits are you EVER able to edit it?
All I was doing was trying to add a new combo box. after adding and saving
the form, I haven't been able to open it.

Rick

"Bob Alston" <bo********@yahoo.comwrote in message
news:6r*************@newsfe02.lga...
Rico wrote:
>Hello,

I have a form that seems to corrupt over and over again. I can't open it
in design view, usually getting a message like "There isn't enough memory
to perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of
controls on the form; there are about 320 controls, but that is still
about half of the Access limit of 754. I also removed about 120 text
boxes and placed them in a subform to reduce the number of controls on
the main form. Any idea what might be causing this problem? at this
point, I feel like I'm spinning my wheels, because I have to keep
restoring from a previous version, then modify and hopefully save a copy
before the form corrupts again. One thing I should add, is the
corruption only happens when I'm modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick



1)Try copying the form in the current database and try editing the copy.

2)Try importing the form into a clean database, that has any source tables
and queries defined.

3) Try saving the sub form and then replacing it with a very simple
subform - to see if that can be edited.

4) After recovering from a previous version, what edits do you do to the
form? After these edits are you EVER able to edit it?

Bob

Oct 16 '07 #7

P: n/a
Rico wrote:
Hi Bob,

Thanks for your advice. I wound up recreating the entire form from scratch,
one control at a time, but, to answer your question;
>4) After recovering from a previous version, what edits do you do to the
form? After these edits are you EVER able to edit it?

All I was doing was trying to add a new combo box. after adding and saving
the form, I haven't been able to open it.

Rick

"Bob Alston" <bo********@yahoo.comwrote in message
news:6r*************@newsfe02.lga...
>Rico wrote:
>>Hello,

I have a form that seems to corrupt over and over again. I can't open it
in design view, usually getting a message like "There isn't enough memory
to perform this operation. Close unneeded programs and try the operation
again.". I can get to the code but can't seem to do anything to get into
design view. The thing I thought about at first was the number of
controls on the form; there are about 320 controls, but that is still
about half of the Access limit of 754. I also removed about 120 text
boxes and placed them in a subform to reduce the number of controls on
the main form. Any idea what might be causing this problem? at this
point, I feel like I'm spinning my wheels, because I have to keep
restoring from a previous version, then modify and hopefully save a copy
before the form corrupts again. One thing I should add, is the
corruption only happens when I'm modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick


1)Try copying the form in the current database and try editing the copy.

2)Try importing the form into a clean database, that has any source tables
and queries defined.

3) Try saving the sub form and then replacing it with a very simple
subform - to see if that can be edited.

4) After recovering from a previous version, what edits do you do to the
form? After these edits are you EVER able to edit it?

Bob

So is it now working OK? If so the problem was probably the lifetime
max on controls. A way around this is to copy the form, delete the
original then rename the copy. works slick. works for tables also.

bob
Oct 16 '07 #8

P: n/a
Can you import the corrupted form into a new blank database? Just that form,
nothing else?

If you can't then i'd give up. If it won't import I'd call it corrupted
beyond repair. Rebuild it from scratch or a usable backup (a backup version
carries a reoccurance risk however, so be careful..).

If you can import it, and can also open it in design view, then the import
*may* have fixed it & you can import all other objects into the new mdb file
and move forward.

HTH,
"Rico" <me@you.comwrote in message news:8Z5Ri.15195$G25.4600@edtnps89...
That would work if I could open the form in design view. ;)
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
>Rico wrote:
>>Hello,

I have a form that seems to corrupt over and over again. I can't open
it in design view, usually getting a message like "There isn't enough
memory to perform this operation. Close unneeded programs and try the
operation again.". I can get to the code but can't seem to do anything
to get into design view. The thing I thought about at first was the
number of controls on the form; there are about 320 controls, but that
is still about half of the Access limit of 754. I also removed about
120 text boxes and placed them in a subform to reduce the number of
controls on the main form. Any idea what might be causing this problem?
at this point, I feel like I'm spinning my wheels, because I have to
keep restoring from a previous version, then modify and hopefully save a
copy before the form corrupts again. One thing I should add, is the
corruption only happens when I'm modifying the design.

Any help or direction on this issue would be greatly appreciated.

Thanks!
Rick

Along with the other's comments...sometimes I open the "corrupt" form and
create a new form and select all controls on the bad form and do and
Edit/Copy from the bad form and Edit/Paste to the new form. Then copy in
the code. Then save the new form, delete the old.


Oct 16 '07 #9

This discussion thread is closed

Replies have been disabled for this discussion.