HELP! Form doesn't exist/TempMSysAccessObjects already exists

[Stephanie]

I apologize for posting this in "forms" - I think this is a better section of
the group.

I'm at a standstill-
Two issues:

1) I was trying to clean up my database and found I wasn't using a form
(FormName). So I changed the name to (~FormName). Then I deleted
(~FormName).

I can no longer see (~FormName) in the database window (where you select
tables, queries, forms...). However, in the VB code window on the side bar,
I see Form_~FormName. When I select the code, I receive an error message
"The form name is misspelled or refers to a form that doesn't exist". True.
But I can't cut or delete the form out of the list of forms.

As you can imagine, my db is not working (at least not the objects that
contain VB) with the bogus reference.

2) When I try to compact and repair, this error msg appears: table
TempMSysAccessObjects already exists. With no opportunity to change the temp
table name (even if I knew what that meant). This is now happening on all
versions of my db (not just the form doesn't exist version of my db). What
does it mean? How can I fix it? I compact and repair often and have never
seen this.

I thought I was doing the right thing renaming the form and then deleting
it. What did I do wrong and can it be saved? Thanks!

 

[Stephanie]

I did solve the TempMSysAccessObjects isuse!!
But I still can't figure out why vb thinks I have a form, but the form
doesn't show in the db window...

 

[Chris Mills]

1) I was trying to clean up my database and found I wasn't using a form

(FormName). So I changed the name to (~FormName). Then I deleted
(~FormName).

I can no longer see (~FormName) in the database window (where you select
tables, queries, forms...). However, in the VB code window on the side bar,
I see Form_~FormName.

You don't say which version, but not to worry the class object Form_~FormName
should have been deleted along with the form. I verified this in A2002.

I think I have seen that in A2000, and the problem is "just" that Access has
trouble keeping track of itself and easily gets "corrupted".

Firstly (I have to say this) take a backup or several before any recovery
attempts.

I would suggest a decompile (/Decompile) to clear out any partially compiled
code.
Decompile/Compile/Repair/Compact is about the best you can do to get rid of
"corruption". Apart from Jetcomp but this appears to be a "code corruption".

Some might suggest Decompile/Repair/Compile/Compact is more sensible order.
Anyway, do them all.

Chris

 

[tina]

if you're using A2000 or newer, try this

open a new blank database.
immediately go to the menu bar and click Tools | Options | General tab.
remove the checkmark next to the "Track name AutoCorrect info" option.
click the Apply button, then the OK button.
compact/repair the database.
import all the objects from your original database (don't forget to import
Menus and Toolbars and Import/Export Specs, if you have any in the original
database).
compact/repair.
if everything now works ok, back up the db, and roll on.

hth

 

[Chris Mills]

import all the objects from your original database

Well, I agree that's a further step, the ultimate way to get rid of
"corruption", but best avoided unless nothing else works. For one, "most"
databases use User Level Security, and that's a pain to set up again...if it
can be avoided.

If there's no User Level Security set up, then I agree, why mess around
there might be other things wrong as well

Cheers
Chris

 

[Stephanie]

Tina,
Thanks for the helpful and quick response! I was in a panic, especially
when none of my db version would compile.
I was able to import into a new database. I do think I have some sort of
corruption, so I ended up using a previous version and pulling what I needed
into it (no doubt, forgetting something!).

 

[Stephanie]

Hi, Chris. I was able to get a mish-mash copy of my db running. I couldn't
figure out how to compile, so I followed Tina's suggestions, only to have a
curruption problem! Anyway, thanks so much for your quick response to my
panic stricken post!
Stephanie

 

[tina]

well, yes, that can happen if one of the objects you're importing (like a
form) is corrupted. i should have said that in my previous post. at least
you're back up and running now!

 

[Chris Mills]

If you have code, then really you have to compile. It tests for code errors,
reference errors, and makes your app run faster! I'd take a backup first, esp.
A2000 was a bit flakey and could "lock-up" on a compile.

In the VBA/code window (<Ctrl G>): Debug, Compile

Chris