asked on

Isn't enought memory error on new subform

I'm design a new subform the will display continuous records. Now I getting the not enough memory error even when I try to go into design view. There is only one record in the table the subform references.

I'm using W7 and the error occurs when I try to access the from in either O2003 or O2010. Is there a way I can get around the error and get into the form using design view so I can fix whatever the problem is?
JR

PatHartman

Most likely the form is corrupted. Try compact, try /decompile, try creating a new empty db and importing all the objects.

SOLUTION

John Tsioumpris

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Jeffrey Coachman

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

JudithARyan

ASKER

I just tried compact, no joy.

I haven't tried the new database and import objects yet.

When I tried the decompile, I got the message that the syntax was wrong. I used the one that John T. showed me. Is it different for A2010?

Thanks

JR

PatHartman

The syntax John posted assumes you have A2007. You need to use the path for your installation of Access. Essentially, the example is starting access with the /decompile switch but not specifying a database. Access opens, you pick a database, and then it decompiles. I can't say that this works since it isn't the method I use. Since Access is registered to open .accdb files, I don't bother with the path to Access at all. I just start what ever app I want to decompile.

C:/f1/f2/appname.accdb /decompile

Just use the full path to your access app.

Scott McDaniel (EE MVE )

Since Access is registered to open .accdb files, I don't bother with the path to Access at all.

I've found this troublesome on my machine, since at times that syntax will open 2007 or 2010, instead of 2013 (which is my main development version). Once that happens, you get the annoying "Please wait, installing blah blah" situation, which means I have to cancel it, and then close down all of my Access windows, and restart them to insure I don't have issues.

If you're only running a single version of Access on the machine you're okay with doing this, of course.

JudithARyan

ASKER

Thanks, guys. After considering everything, I decided to redo the form. I'm save each step, so if it happens again maybe I'll have some idea of what I'm doing wrong.

HR