form name changed by system

[AdamFeerst]

Access changed the name of a form, forcing me to do a SaveAs. Now, I am not able to rename the form, or copy it under any new name - "Name conflicts with existing module, project, or object library." This happens too when I try to import the form into a new database. In VBEditor, the code appears under the name of the original form. I don't see the new name in VBEditor.

How can I get the form name back? I've already tried Compact and Repair, and importing all the form elements into a new form.

 

[GohDiamond]

What was the name of the form before it was changed? You may be trying to use a reserved word.

Goh

 

[AdamFeerst]

Not reserved. "frmParentInfo" Was working well before this.

 

[GohDiamond]

Try :https://msdn.microsoft.com/en-us/library/office/ff823209.aspx

In the VBE Immediate Window

DoCmd.Rename "frmParentInfo",acForm, "frm_CURRENTNAMEHERE"

Capture any Error message if you get one, and let us know.

Cheers!
Goh

 

[missinglinq]

This type of thing comes under what I call Strange, Odd and Curious Behavior, and S/O/C/B usually translates into corruption, hopefully of the single Form, but possibly of the entire database!

The first thing to attempt, for this type of corruption, is to create a new, blank file and import everything into it. Only takes a minute or two to create and check out, and if it doesn't work you haven't really lost anything! And, amazingly, it does frequently work, while moving the Form into another Form usually doesn't!

Linq ;0)>

 

[AdamFeerst]

Goh,
The error message is what I originally posted, "Name conflicts with existing module, project, or object library."

I went to a backup version from a couple of days ago. Reminds me that I need to (and not just say I will) make a copy at the start of every day, before I start working on it.

 

[AdamFeerst]

Another SOBC, when I go to design mode in formA, formB closes, and vice versa. As far as I can tell, that doesn't happen with any other forms, either causing others to close or being closed.
Related?
Corrupted?
New/blank and import everything?
Do I hear Twilight Zone music?

 

[GinaWhipp]

Have you brought everything into a *clean* database?

 

[missinglinq]

Added to your other info, I'd opt for the database itself being corrupted! Gina asked, and I repeat, have you done the procedure suggested in Post #5...creating a new, blank file and import everything into it?

Linq ;0)>

 

[AdamFeerst]

I agree. It turns out that one of the SQL BE tables has some duplicate records, I'm not sure how that could've happened since it violates data integrity rules. I think I need to clean that up first.

 

[AdamFeerst]

I have created a new database and imported everything, but I am still getting SOBC. When I go to design mode in formA, formB closes, and vice versa.

Any other thoughts?

 

[Galaxiom]

I agree. It turns out that one of the SQL BE tables has some duplicate records, I'm not sure how that could've happened since it violates data integrity rules. I think I need to clean that up first.

Access can show duplicates on an ODBC linked table that doesn't actually have duplicates if the key fields have not been appropriately selected to define unique records during the import.