Ms Access Form won't open

I had a msgbox pop up and tell me there wasn't enough memory to save.  Please close some other applications then resave.

So i did this, but now i have a form that will not open it design or in normal mode. I can access the code module. but i can't get the form to  open.  

I really don't want to start from stratch with a new form.

Does anyone have any ideas.

I compacted and repaired the db as well. No luck though

i also restarted laptop.

j_BryanAsked:
Who is Participating?
 
harfangConnect With a Mentor Commented:
Hello j_Bryan

I'm afraid this is a symptom of database corruption. This occurs frequently when you are editing the code module of an open form. We all do it, naturally, because it's so convenient, but sometimes VBA gets confused in its dozen of compilation levels of a module and saves the wrong one.

At that point, the form is no longer accessible by any normal means (opening, copying from another database, etc.) and often cannot even be deleted. In those cases, I create a new blank database, import all surviving objects from the corrupted database, and import the victims from my last backup. I do an hourly backup when designing for that exact reason.

There might be companies who will claim to retrieve portions from such a corrupted database, but I never took the trouble and -- sometimes -- had to start from scratch.

Sorry for the bad news.

Last thing to try (very little hope): decompile your DB:

    "<path to access>" /decompile "<path to your db>"

Cheers!
(°v°)
0
 
harfangCommented:
Wait, if you can still see the module, at least copy-paste that to a text file. You can also try (again, very little hope) from the VB immediate pane:

    SaveToText acForm, "frmBuggyForm", "C:\buggyform.txt"

And then, in a new blank database:

    LoadFromText acForm, "frmRetrieved", "C\buggyform.txt"

(°v°)
0
 
clarkscottConnect With a Mentor Commented:
Try creating a new mdb and import it.  Sometimes this works.
Actually, I just had a form crash on me.  I did this procedure and all was fine.  I simply deleted the original (bad) mdb and renamed the new one.

Saved me about 2 hours of work.

Scott C
0
 
Leigh PurvisConnect With a Mentor Database DeveloperCommented:
Incidentally - what version of Access are you using?
I ask because this behaviour used to be much more common back in Access 2000.  (It's early days - before the SP rescuers).

If it is A2K make sure you're Service Packed all the way.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.