out of memory erro

[Rocky]

I am working with Access 2003. I am creating a form with 20 pages on a tab
control. I have loaded each page with text boxes and combo boxes from the
various tables in the database. I am in the process of editing the layout and
row source for the combo boxes and text boxes. Usually after saving changes
in design view and then attempting to go to form view, I get the error
message, "there isn't enough memory to perform this operation. close unneeded
programs and try the oepration again." Interestingly, this usually only
happens after I have gone through the process of editing the form, saving it,
displaying the form view and then attempting to repeat the cycle that I get
the error message.
I have attempted to find answers in the knowledge base, but it references
grouped controls which I do not have and changes relative to Service Pack 3,
that I don't think apply to my situation.
Any ideas as to what is going on?
Tx

 

[Rocky]

That might be a problem, it will take me a little while to have a look.
Tx
Rocky

 

[John W. Vinson]

I am working with Access 2003. I am creating a form with 20 pages on a tab
control. I have loaded each page with text boxes and combo boxes from the
various tables in the database. I am in the process of editing the layout and
row source for the combo boxes and text boxes. Usually after saving changes
in design view and then attempting to go to form view, I get the error
message, "there isn't enough memory to perform this operation. close unneeded
programs and try the oepration again." Interestingly, this usually only
happens after I have gone through the process of editing the form, saving it,
displaying the form view and then attempting to repeat the cycle that I get
the error message.
I have attempted to find answers in the knowledge base, but it references
grouped controls which I do not have and changes relative to Service Pack 3,
that I don't think apply to my situation.
Any ideas as to what is going on?
Tx

For one thing... that's a TERRIBLY heavy form, and suggests that you're trying
to make that one form do every imaginable function of the database. Is there
some logical way to split this up, so that you can (say) use a switchboard to
open different forms for different functions, or have command buttons on one
form to pop up another form? I have some busy forms in my apps, but nothing
like that!

For another, the (bogus) "out of memory" error is one that's burned me. It can
happen when a VBA project becomes corrupt, or when a Form gets corrupted. I've
had to delete and rebuild a form, or (a bit less drastic) create a new
database file; decompile the old database; import all the forms, reports, etc.
and recompile, and finally compact and repair the new database.

I'd really suggest first checking that your table structure is properly
normalized, and see if you can't come up with a user interface that isn't so
dependent on one massive, complex form.

 

[Rocky]

John,
I think you are right on with your suggestion to use a switchboard to open
different forms. This is my first experience with using more than a couple
of pages on the tab control and now realize that it is not built to use many
pages as I initially tried.

To answer your question about the database; I am writing an application for
a database designed by a national organization which allows different front
ends to input the data. I believe the database itself is well normalized.

I certainly hope I don't have to reconstruct any of the database tables, as
you can guess, it is a large database and took some time to construct.

I will go with the idea of a switchboard and command buttons to open several
forms as a workaround and get back to the community if I run into trouble.

Thanks for your suggestions.

Rocky

 

[John W. Vinson]

To answer your question about the database; I am writing an application for
a database designed by a national organization which allows different front
ends to input the data. I believe the database itself is well normalized.

If your multiple pages are in fact different user interfaces then I'd
ABSOLUTELY use different forms - perhaps even different frontend .mde files,
if the different front ends are used by different people in different places.