What's up with Access renaming things for me?

[jsteph]

I've renamed some tables in order to specifically remove them from any possibility of being involved in processes because I'll be testing with them, and using dummy data.

So I rename them prefixing with 'zz', so I can save the structure in case I want to put it back into use. I have querys used in a production process that *may* have used the original table, and--hard as I try--I may not find them all in order to put the new table in them, or to remove the querys from the processes. So I figure I'll run a test go of the process--and then I'll see where the error "ms jet can't find the table nnnnn" or whatever comes up, and then deal with it.

So I run the process to test, and no errors. Great. Now live. No errors, but bad data is the result. Why?? Because Access re-coded the sql in the query behind my back and put the 'zz' prefixed table in that query!! Without telling me! I had run speed ferret after renaming to find instances of the 'orphaned' table and it came out empty, thanks to MS renaming it. So a production process ran with the test data! Being Access, it wasn't critical, but it's still unnerving to have some invisible elf changing your code without telling me.

I assume this is some 'option' or 'feature'? Does anyone else find this atrocious? And how do I turn this off??

Maybe I'm just stressed out but this is the first time I've run across this and I find it monumentally disturbing. Let's face it--this is Access, and this is the real world--so we don't all have a Dev, QA, and Prod version of our .mdbs so we won't always catch this stuff, and I just find this amazing that something like that is out there.
--Jim

 

[SgtJarrow]

Most Likely:

Tools -> Options General Tab Name AutoCorrect Section

=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)

Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
VB/Access Programmer

 

[jsteph]

Thanks very much!
--Jim

 

[JoeAtWork]

The "Autocorrect" feature has proved to be very buggy and most programmers turn it off. It tends to noticeably slow down the system and can even be the cause of corruption. It often doesn't even do what it's supposed to, leaving inconsistent updates. One of those things that makes you wonder if the marketing people insisted on "releasing a new feature" over the objections of the quality control people.