Decompiling?

[MikeB]

I've been messing around a lot in my Access database, renaming tables,
fields, deleting queries etc.

I've seen a few threads here where people have been advised to turn
off auto-renaming, other threads referring to decompiling as well as a
few references to other ways of generally cleaning up an Access
database.

Are these things necessary? Is the auto-renaming feature prone to
corruption?

Should I be doing any of these steps? If so, is there a step-by step
list of things to do somewhere on the Internet?

Thanks.

 

[Douglas J. Steele]

Not sure about Access 2007, but in previous versions of Access, Autocorrect
was very prone to errors (hence the common referral to it as Autocorrupt!)

Check what Allen Browne has at http://www.allenbrowne.com/bug-03.html

 

[MikeB]

Not sure about Access 2007, but in previous versions of Access, Autocorrect
was very prone to errors (hence the common referral to it as Autocorrupt!)

Check what Allen Browne has athttp://www.allenbrowne.com/bug-03.html

I'm still using Access that was part of Officce XP (Access 2000?)

This laptop computer is older and I'm not so sure I can afford
(performance-wise) installing Office 2007 on it. I have 2007 on my
desktop.

 

[Arvin Meyer [MVP]]

"AutoCorrupt" was never reliable anyway. I always used Speed Ferret for the
few times I need to make changes. Decompile and Compact at least once, at
the end of development, cleans out any useless junk left behind from
deletes, etc. and presents a pristine database, ready for production.

Office 2007 does take quite a bit of resources. On Vista, I would recommend
no less than 2 GBs of RAM. I use 3 and 4 GBs on my newest machines.