HELP!! Report destroying database!

[The Bey]

I'm in the midst of a meltdown. Yesterday I changed the name of a report and returning to my work today it seems that my database will barely function.
The report is opened through various lines of code based in forms but it doesn't have a massive part to do with my database.

Anyway, almost everything I try to open it says that I'm missing a module and then when the code opens it keeps flashing up saying the report name is misspelled or doesn't exist. When I try to change the name of the report it just autocorrects itself to the name I gave it last night.

I've been making backups of my database but usually after I've done something big... I'm actually saving it in the wrong order, as I should save before the big change. Anyway, what I'm saying is that I could go back to a previous one and go to where I hadn't changed the name, but there've been more changes on the database since then so It'd be much better if I could just fix this error. Any thoughts??

I'm going on holiday next week and I don't want this bloody database to keep my head at home!!

 

[The Bey]

Ok I think I avoided it; I just recreated the original report with the same name and it seems that everything's in order again.

I got out of this one ok it seems (well, it does at the moment) but if anyone's had a problem like this could you post a response as I don't like near misses like this and it'd be nice if I could help other people if they have this problem

 

[Galaxiom]

I would definitely go back. It is safer. The major problem you have now may only be the beginning. Changing names of objects is a big undertaking and requires a thorough retest of the entire database. It is not something to be done casually.

You would need a very good reason to change a name. Why did you make this decision?

When an object name is changed the NameAutoCorrect only changes some instances of the name. The name is not changed in VBA and other strings. If there is a reference to a module in the code that will return the error about the module. Referring to the Report in any module will throw errors.

NameAutoCorrect is also known to cause corruption. Some developers call it NameAutoCorrupt.

In my experience I suspect it gets confused if the new name of the object is shared with the name of a control anywhere in the database.