Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Forms / April 2008

Tip: Looking for answers? Try searching our database.

Global Default Options

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
MikeV06 - 17 Apr 2008 00:54 GMT
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
Jeanette Cunningham - 17 Apr 2008 01:45 GMT
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

> Compact on close has to be set by database. I have a bunch of databases
> for
[quoted text clipped - 7 lines]
>
> Mike
Linq Adams - 17 Apr 2008 03:23 GMT
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.

Signature

There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

MikeV06 - 17 Apr 2008 13:57 GMT
> 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
Jeanette Cunningham - 17 Apr 2008 22:23 GMT
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

>> Quite simply, you should never compact without backing up you db first,
>> for
[quoted text clipped - 12 lines]
>
> Mike
MikeV06 - 18 Apr 2008 01:00 GMT
> Mike,
> the other main culprit is the AutoCorrect feature.
[quoted text clipped - 4 lines]
>
> Jeanette Cunningham

One more thing to worry about. Thank you for the warning.

Mike
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.