Not Enough Memory To Open Form Message

[EarlCPhillips]

I have a Contact Management form for outreach that contains four sub forms.
Things worked well until I added the fourth subform. The first three are
addresses, phones and email addresses. The fourth is for case histories
related to this contact.

Now it fails to open even in design mode with the message that there is "not
enough memory to open the operation, close other programs to perform this
operation." But there are no other operations open.

How do I revert to a prior version? Even deleting the fourth subform does
not help. Help!

EarlCPhillips
Volunteer Ex-mainframer Learning Access To Help
Local Food Bank Feed the Hungry More Efficiently

 

[a a r o n . k e m p f]

wow sounds to me like you should be using SQL Server

jet just isn't reliable enough for anything along those lines

sorry

if you were local; i'd help you directly

-Aaron

 

[Tom Wickerath]

Hi Earl,

First, please ignore the reply that you received from Aaron Kempf. His
suggestion for *everything* is to upgrade to SQL Server. Oh, but he
inadvertently failed to mention that SQL Server has no real provisions for
creating a user interface. Typical Aaron. Just ignore him.

You didn't say which version of Access that you are using, but if you are
using an unpatched copy of Access 2000, then updating to Service Pack 1 (and
ultimately to SP3) may solve your problem:

You receive "There isn't enough free memory" error message
when you work with a Form in Access 2000
http://support.microsoft.com/kb/236977

Here is another KB article, although this one seems to deal with startup
errors:

ACC2000: Resolving "System Error or Not Enough Memory to Start"
Error Messages
http://support.microsoft.com/kb/217353

If you are not using Access 2000, then you may have one or more corrupt
forms. The first thing to try is to import all objects into a new database
container. I give complete instructions for how to do this on the bottom half
of page 3 of a Word document that I call Access Links. See the section titled
"My standard advice for attempting to fix minor corruptions". You are welcome
to download a zipped copy from my web site:
http://www.accessmvp.com/TWickerath/

If this does not work, then we may be able to recover the affected form(s)
using a few other methods. I can write more about these other methods if the
above method does not work for you.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[EarlCPhillips]

As I was musing on this last night it occurred to me to use the Compress and
Repair command. It worked. I am now rebuilding the subform and will go from
there.

Thank you all for the help. I downloaded Tom's paper on Access Links to
learn more. Harvesters is using Access 2003 and will soon move to Access
2007. There is only one operations person here and I am the other IT staff,
and a volunteer at that. I did mainframe programming and some PC development
and cross platform work, but that was seven years ago when I retired. The
hungry need us so desperately and Harvesters can use all the help it can get
what with the state of the economy and the slow-down of donations here.

Bless all who try to help me help them.

EarlCPhillips
Ex-mainframer Learning Access To Help
Harvesters Feed the Hungry

 

[Tom Wickerath]

Hi Earl,

If you can send me a copy of your database, I will volunteer to run an
analysis of it for you, using my copy of Total Access Analyzer
(http://www.fmsinc.com/products/analyzer/index.html). I do not need any of
the data in the tables, so if anything is considered sensitive data, you can
delete all records from the tables in a *copy* of your database. Then do a
Compact and Repair.

My e-mail address is available at the bottom of the contributors page (link
shown in signature). If you are interested, send me a compacted--and
preferably zipped--copy of your database. Please do not post your e-mail
address (or mine) to a newsgroup reply. Doing so will only invite the
attention of spammers.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Pi]

Hi Tom,

You seem to be very knowledgeable in Access. I'm receiving a similar type
of error on one of my forms. The form will open in design mode, Form View
and Datasheet view, but when I try to open the Record Source from the
properties menu it gives me the error "There isn't Enough Memory to perform
this Operation. Close unneeded programs and try the operation again".

The control panel shows 649,000 memory available out of 1,309,928.

Does Access have a limited number of parameters that can be used on a query?

I am able to copy the SQL code to another query, but I get the same results.
If I delete everything after the Where statement then it will open in the
Query Design View.

I've tried compact and repair and copying everything over to a new Databse
with the same results.

I'm trying to use the following parameters on 15 fields.
Like Forms!FrmFilterEQMain!AssociatedEquipID Or
Forms!FrmFilterEQMain!AssociatedEquipID Is Null

In other words if the Parameter field on the form is null then return all
values.

Any help you could provide would be appreciated.

Thanks,

Kathleen

 

[david]

I am able to copy the SQL code to another query, but I get the same

results.

Copy the SQL to another query,
Open the form(s) in Form View,
Then open the other query.

You probably can't open the query unless it can evaluate those terms.

I normally make a saved query without the where clause, then use that
as the base for SQL in the form. That allows me to check the query
without having the form open, and also sometimes avoids this problem


Yes, Access has a limited number of parameters, but I don't think that
is your problem.

(david)

 

[Pi]

Thanks David,

I will eliminate the critera from each field one by one untill I find the
field that's giving me the trouble.

Kathleen

 

[Pi]

I figured it out

In the imbedded query in the form I inserted the criteria:
â€Like [Forms]![FrmFilterEQMain]![Unit] or [Forms]![FrmFilterEQMain]![Unit]
is nullâ€

Access creates a 2nd data field named as the form control
[Forms]![FrmFilterEQMain]![Unit] and sets the criteria to is null and removes
the “or’ condition from the original expression.

For each field that I use the expression “Like or is null†Access duplicates
the criteria for each field and adds another row of “is null†criteria.

So having 15 fields with this expression “Like or is null†creates a vast
amount of criteria data and causes an error when trying to view the query in
the Design View.

I suspect there is a limit to the number of rows a query can contain.

Kathleen

 

[TinMan]

Hi Tom, I hope you are still available to help. I have the same problem. A
main form with sub forms. I have tried adding another form but as soon as add
this form to the main form. The main form reports the error. I can't open it
in design view either. If i delete the subform it doesn't cure the error
message. The sub form opens by itself and no problems opening the table. I
have deleted the main formand tried numerous time but same problem. I have
also tried importing all into new db but get the message as the form is
analysed and doesn't import. Can you please help me??!!

 

[Paul Shapiro]

If everything BUT that one form imports successfully to a new blank db, that
might be indicating the form is corrupted. Try importing JUST that one form
into a new blank db. If it still fails, you can either try loading an older
version of the form from a backup, or exporting that form to a text file
using the undocumented Application.SaveAsText command:
Application.SaveAsText acForm, "formName", "C:\Path\OutputFile.txt"
and then importing it to a blank db using the equivalent LoadFromText
command. These are the commands used by the Access Sourcesafe integration to
put objects to and from text format.

If that still doesn't work, you can try looking at the .txt file to see if
you can find the problem. Try saving a similar but working form to text and
see if you can find the difference. Might not be so easy.