Changing names of tables, forms, reports etc

[RenaG]

Hi,

I inherited a database that has a ton of tables, some forms and some reports. The original programmer did not use the typical naming conventions for any of these so I have a table called FollowUp, a form called FollowUp and a report called FollowUp (as an example). I would like to change it to tblFollowUp, frmFollowUp and rptFollowUp. If I do this, will Access cascade those changes throughout the database? It is so big and complicated that I don't want to get myself into trouble so any suggestions on how to approach this would be appreciated.

TIA!

~RLG

 

[Galaxiom]

What you are proposing is absolutely not worth the grief. Access will cascade some changes if you have NameAutoCorrect on but it won't fix the VBA and misses the names in SQL RecordSource queries too.

You would have to do a thorough and complete retest of absolutely everything in the database. Missing somethng is almost inevitable.

You also risk NameAutoCorrect causing corruptions to objects. These breakages can be very difficult to track.

Even using the Find and Replace functionality in somethng like V-Tools will be a struggle because you are wanting to selectively change one string to multiple variations.

Access knows the difference between the tables, forms and reports and if you care to consider, it is also obvious in code. Forms!somename, Reports!somename and somename are all quite obvious.

In the VBA
Docmd.OpenForm "somename" is obviously a Form.
DoCmd.OpenReport "somename" is obviously a Report.

Hungarian notation is a convention, not a law. Moreover, many developers don't use it. Personally I find its advantages grossly overstated.

 

[plog]

Agree with Gala completely.

Hungarian notation is a convention, not a law. Moreover, many developers don't use it. Personally I find its advantages grossly overstated.

I've felt like I was the only one who saw that the emperor had no clothes.

 

[RenaG]

Hello Galaxiom,

That is exactly what I needed to hear. Thanks so much!

~RLG