The form name is misspelled or doesn't exist

[Dale Fye]

I brought some work home this weekend and created a couple of new forms.
Everything worked well (both home and work are using A2k3, SP3). I brought
my db back into the office this morning, and started having problems almost
immediately. Access didn't like one of the forms I created, so I created a
new database, turned off Track Autocorrect, then imported all of the objects
except the offending form into the new db.

Copied an existing form and named it "frm_Solution_Synthesis", modified all
of the code behind the form, queries etc for this form. Ran the application,
including this form, and it worked fine. Closed the file (compact on close
was turned off). Came back 30 minutes later and am now getting a message
that reads:

The form "frm_Solutions_Synthesis" is misspelled or refers to a form that
doesn't exist.

When I look at the Form objects, the form is missing, but when I look at the
Class Objects in the VBA editor, the form shows up. Any ideas what is going
on?

There is nothing special about this form, it has(had) a tab control with a
couple of tabs, is bound, and has a listbox on one of the tabs.

I have never run into this type of problem before, and would really
appreciate some help ASAP.

 

[Dale Fye]

Marshall,

Thanks for your response. If I interpret your comment correctly, what I
think you are telling me is, "Oh, well", and "Try again".

I've been using access for over 10 years now, and don't recall ever running
into this problem before.

I have dual monitors, and when I am debugging, I generally run my code and
forms side-by-side, making changes to code as needed, with the form loaded.
I have never seen this before (although I've only recently upgraded both my
home and work systems to A2k3, SP3).

As for this particular form, as far as I can recall, all of my code edits
were done with the form in design mode.

Dale
--
Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

 

[Marshall Barton]

I brought some work home this weekend and created a couple of new forms.
Everything worked well (both home and work are using A2k3, SP3). I brought
my db back into the office this morning, and started having problems almost
immediately. Access didn't like one of the forms I created, so I created a
new database, turned off Track Autocorrect, then imported all of the objects
except the offending form into the new db.

Copied an existing form and named it "frm_Solution_Synthesis", modified all
of the code behind the form, queries etc for this form. Ran the application,
including this form, and it worked fine. Closed the file (compact on close
was turned off). Came back 30 minutes later and am now getting a message
that reads:

The form "frm_Solutions_Synthesis" is misspelled or refers to a form that
doesn't exist.

When I look at the Form objects, the form is missing, but when I look at the
Class Objects in the VBA editor, the form shows up. Any ideas what is going
on?

There is nothing special about this form, it has(had) a tab control with a
couple of tabs, is bound, and has a listbox on one of the tabs.

I have never run into this type of problem before, and would really
appreciate some help ASAP.

That sounds like the corruption is still there or you caused
the same thing again. In my experience, that kind (among
several others) of corruption is caused by editing a form's
VBA code while the form is open in any view other than
design view. It's a difficult habit to get into, but you
should **never** edit a form or report's code unless you
first switch to design view. I have had this happen when I
inadvertantly typed a space while just looking at a form's
module.

When you import everything into a new blank mdb file, be
sure to select each form separately (i.e. do not use Select
All and uncheck the form you want to leave behind).

 

[Dale Fye]

Thanks, Marsh.

I think that was the piece I was missing.

I followed your instructions about importing the forms (clicking on each one
individually) and created a new one, and have it working again.

Dale

 

[Marshall Barton]

Thanks for your response. If I interpret your comment correctly, what I
think you are telling me is, "Oh, well", and "Try again".

Pretty much, yeah, that's what I'm saying. It is important
to not use the Select All button when importing all but the
damaged form. Select All will pick up any ghost forms (and
reports) that were not completely removed (you said the form
is not in the db window, but it is in the project's objects
list).

 

[Christine Seager]

Marshall:

I recently started encountering the same corrupt database issue Dale
experienced, but not just in one database but three different databases.

I am quite guility of making changes in the code module without having the
form open in design view, and have been following this bad same practice for
years without any problems. I also have been modifing the databases using
several different computers and not experienced the corruption error before.
However, I followed your instructions in this post on all three databases.

I replaced one database which is being shared on a network drive. The first
user was able to open it, make changes, etc. without issues. The next user
opened it reviewed the changes, may or may not have made changes. When the
original user attempted to get back into the database he received the same
error all over again.

This issue recently started occuring and the company I work for recently
started beta testing Office 2007. Some of the database users have Access
2003 and some Access 2007. Regarding the database mentioned above, the
first user was using Access 2003, the second user Access 2007. I believe
the same scenerio occurred with the other two databases, but can not confirm
it yet.

Could Access 2007 be having an impact on the database which is rendering it
useless for Access 2003 users?