If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Global Default Options
Mike,
if these databases are split, it is only the backend that needs compacting usually. There have been some reports of compact on close being a cause of corruption or errors in split databases in a multi-user situation. If your databases have not been split and are just single-user, compact on close will probably work OK. I have seen some code or an add-in that allows you to compact a database by right clicking it in the explorer window. Sorry I don't have the details at hand. You could do a search on that. Jeanette Cunningham "MikeV06" wrote in message ... Compact on close has to be set by database. I have a bunch of databases for which I would like that to be the default as well as new databases. As of now I open the database, set the option, close the database. I am not comfortable compacting using tools, compact since it does not remember the name I am compacting and I want to move it to a new folder with the same name. It is a pain trying to remember the original name and type it. Thanks. Mike |
#2
|
|||
|
|||
Global Default Options
Quite simply, you should never compact without backing up you db first, for
the reasons Jeanette gave. The reports I've seen, here and on the other five forums I visit daily, suggest that this problem is not limited to split/multi- user databases. -- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#3
|
|||
|
|||
Global Default Options
Mike,
the other main culprit is the AutoCorrect feature. For every database, go to Tools | Options | General and turn off Auto Correct. Here is a link to a page about corruption http://www.granite.ab.ca/access/corruptmdbs.htm Jeanette Cunningham "MikeV06" wrote in message ... On Thu, 17 Apr 2008 02:23:24 GMT, Linq Adams via AccessMonster.com wrote: Quite simply, you should never compact without backing up you db first, for the reasons Jeanette gave. The reports I've seen, here and on the other five forums I visit daily, suggest that this problem is not limited to split/multi- user databases. Uhm, thank you both for the warning. I will be a bit more careful about compact. Are there any characteristics of the databases that get corrupted that are consistent so that one can be particularly watchful for that situation? Thanks. Mike |
Thread Tools | |
Display Modes | |
|
|