Not enough memory???

[Tony Williams]

I've a database which is about 46mb big. I've 1gb of memory in my desktop.
When I try and open it I get a message to say there isn't enough memory to
open the file close all unneeded applications. There aren't any others open.
I've tried creating a blank database and importing all the files but get the
same result. Anyone any ideas? I'm running XP Pro with Access XP.
Thanks
Tony

 

[scubadiver]

have you tried compact and repairing to reduce the memory?

tools -> database utilities

 

[Tony Williams]

Yes I did that and the same thing happened. When I tried to import to an
empty database I also got the message when it reached one of the forms so
I'm wondering whether that form has become corrupt. But would I get that
message with a corrupt form?
Tony

 

[Jeff Boyce]

Tony

This is just a wild aside ... is there a chance at least one of your tables
has a record that exceeds the (?2,000 byte) limit?

You could narrow down what may be causing this problem if you create a new
blank database and import one table at a time, checking after each to see
which one "breaks" it...

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Tony Williams]

Hi Jeff, see my previous post I think it may have something to do with a
corrupt form?
Tony

 

[Jeff Boyce]

Tony

A message about memory when there was a corrupt form would not be the most
unusual (read "non-communicative") error message you might see <g>!

If you can import everything except that form, if you don't have a backup
copy of the db that you can import an (old) copy of the form from, you get
to rebuild it! (I'm not aware of a way to "export" the form definition, but
maybe other readers are...)

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Beetle]

Yes, you will sometimes get that message when you have a corrupt form. if
the form happens to one that is used as a startup form, then that may be
why your db won't open. Try bypassing the startup options (hold down the
shift key) while opening your db, then open try opening each form. If you
find the bad one, try replacing it with the one from your most recent working
backup (you have backups right?). If you have no backups, you may have to
delete and recreate that form. If the form happens to have alot of code behind
it, you will want to copy the code before you delete it, then paste it back in
after you create the new form, just make sure you name everything the same
on the new form.

 

[Tony Toews [MVP]]

Yes I did that and the same thing happened. When I tried to import to an
empty database I also got the message when it reached one of the forms so
I'm wondering whether that form has become corrupt. But would I get that
message with a corrupt form?

Definitely that could be the cause. I'd try importing all the other
objects into a new database to ensure nothing else is corrupted.

Then either import that form from a backup if no changes have been
made. Alternatively try the following.

Corrupt Objects within a Corrupt Microsoft Access MDB
http://www.granite.ab.ca/access/corruption/corruptobjects.htm

The little documented SaveAsText and LoadFromText may help if an
object is corrupted or otherwise behaving weirdly.
At the debug/immediate window type:
Application.SaveAsText acForm,"MyForm","c:\form.txt
You can load the file into a new MDB.
Application.LoadFromText acForm,"MyForm","c:\from.txt"

Sample code at http://www.datastrat.com/Code/DocDatabase.txt for
saving all objects in an MDB.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Williams]

Thanks to all who responded. The problem was the form. It was also the
start-up form. I renamed it and imported a copy from a backup copy (phew!
yes I had a backup, things like this are a salutary lesson) After doing that
it worded just fine.
Thanks again
Tony

 

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

move to SQL Server-- it 'just works'.

-Aaron