Compact/Repair Question

[Montez659]

Is there any reason for a front end to be compacted and repaired regularly? I used to have the setting compact on close checked so it would do it every time. Unfortunately, I found out that doing so was causing the front end to "save" and since it resides on my user's desktops, the icons were moving every time they closed the database.

 

[Joe4]

Since the front-end does not hold any of the data, it should not have the same bloating issues that the back-end may have. So it wouldn't seem as necessary to Compact and Repair the front-end as much (if at all).

One recommendation I found is to simply re-propragate a copy of the front-end to everyone occassionally (http://www.consultdmw.com/compact-access-database.htm).

 

[Montez659]

Thanks! I appreicate the info!

 

[SydneyGeek]

Chucking in 2 cents...

I usually back up the front end before making big changes. That way you have a working version if something goes pear-shaped.
I also use SaveAsText to push all objects in the front end out to text files -- but I compile the code before doing it. It's then possible to use LoadFromText to reimport those text files, and rebuild an error-free front end. See this page for a very brief description...

The reason for doing this is that the front end is more prone to corrupting than the back end, in my experience. By round-tripping the code objects (forms, reports, modules) you clear out any metadata that could cause the corruption. You also end up with a nice, compact front end.

Denis