Compact and Repair an Access Runtime Application

[Mimadocken]

I'm building a Runtime app in Access 2007 that will be run by many people who are quite INexperienced with computers, and will have even less experience with Access. Is there a SAFE way to compact and repair an Access 2007 Runtime program?

I keep seeing warnings about using the automatic compact and repair in the Access Options of 2007. However, I'm worried about data bloat if this is never done.

Does anyone out there have experience with Access 2007 Runtime using the automatic compact and repair?

Thank you VERY much for any advice you will share.

 

[GinaWhipp]

Seems like I've answered this already...

There is no need if the database is split. I have front ends that are running for years and have not been compacted. The data is in the back end and even those don't need to be done. If you are running MAKE TABLE queries or other action queries and ALOT of them then just replace the front end, don't bother with C&R.