There isn't enough memory .....

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

Hi

I have this mde that have this error "There isn't enough memory to perform
this operation. Close unneeded....."

This is a front-end ms access 2003 SP3. The other computers are working
fine. Is it bcause its SP3? I haven't updated the others (not even SP1) as
it is working fine for the past few years.

How do I overcome this issue?

Many thanks in advance.

Richard
 
it's because you've been listening to the crackers around here.

Jet is too buggy for real world usage.

Honestly-- move to SQL Server and you'll have enough memory to go
around.
SQL Server is just about 3 times more efficient when it comes to
hardware resources.

-Aaron
 
Often this is caused by having Name AutoCorrect turned on. It could be that
the database is corrupted. First, no matter what, turn off AutoCorrect:

Tools >>> Options >>> General tab

Now make several copies of your database and first try:

http://www.datastrat.com/Code/DocDatabase.txt

to make a backup of everything but the tables. Follow the directions to
restore from the backup into a new database.

If that still doesn't work:

Remember, always work on a copy of the database. Working on the original may
make it impossible for a repair service to fix it.

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Try backing up your forms as text with the undocumented SaveAsText
LoadFromText functions:

http://www.datastrat.com/Code/DocDatabase.txt

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

http://www.granite.ab.ca/access/corruptmdbs.htm

for some suggestions. Unfortunately, some corruption cannot be fixed - you
may need to create a new database, import what can be salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com
 
Aaron, if I upgrade to SQL Server, I will still need to have a front-end.
And I have been using access for years without any problems. Anyway, I am in
the midst of upgrading to Sql Server.

Thanks for your input, anyway

Richard

it's because you've been listening to the crackers around here.

Jet is too buggy for real world usage.

Honestly-- move to SQL Server and you'll have enough memory to go
around.
SQL Server is just about 3 times more efficient when it comes to
hardware resources.

-Aaron
 
Hi Arvin

The auto-correct is off. It is the same front-end application for all the
users. The other users do not have the problem.

I can oopen tables, and run queries but not forms and reports.

Richard
 
Sorry, let me rephrase the answer.

The other users are using the same fe application that is copied from the
server to their individual computers. Could it be becouse of access on that
particular computer? Will reinstall and try.

Richard
 
CAUTION!
It has been determined that the message below was generated
programmatically, by a program robot ("bot") which also allows manual
intervention. This robot was created by a person or persons deliberately
trying to interfere with users of the Microsoft Access database software, and
uses the name of an actual person. As it is not possible to block posting by
this "bot", we post these cautions lest you be misled into taking the posts
as authentic and serious.
 
use Access as a front end then.

But use Access Data Projects-- not linked tables

Things just work.

The # of steps to bind a form to a sproc using JET?
ABOUT TWENTY. Change arguments-- change parameters-- using DAO.

The # of steps to bind a form to a sproc using JET?
ABOUT ONE. You write the sproc. It binds to controls on the forms
automagically.

I usually just set the RecordSource programmatically--- becuase I have
more control that way.

-Aaron
 
nice try buddy-- I'm the only person on this newsgroup with the
ability to come to their own decisions.

Everyone else is a follower.

Now _WHO_ is a robot?
 
CAUTION!
It has been determined that the message below was generated
programmatically, by a program robot ("bot") which also allows manual
intervention. This robot was created by a person or persons deliberately
trying to interfere with users of the Microsoft Access database software, and
uses the name of an actual person. As it is not possible to block posting by
this "bot", we post these cautions lest you be misled into taking the posts
as authentic and serious.
 
Back
Top