Prev: 2 independent criteria in query
Next: Unlock table
From: MichelleM via AccessMonster.com on 5 May 2010 09:16
This may be a dumb question, but I truly do not know what to do. I created a
database for myself, no one else uses it. I have selected the "Compact on
Close" option, but when I go to the location to open it again, I see the
original file with a large file size and then a file name, "db1.mdb" with the
smaller, compacted size. This just started happening in the last week,
otherwise it has always compacted correctly. Any help would be appreciated!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access/201005/1

From: Tom van Stiphout on 5 May 2010 09:46
On Wed, 05 May 2010 13:16:57 GMT, "MichelleM via AccessMonster.com"
<u44423(a)uwe> wrote:

Turn that option off. It was one of those occasional bad ideas coming
out of the Access development team. Compact when you need to, which is
usually much less frequently than at every exit.

-Tom.
Microsoft Access MVP


>This may be a dumb question, but I truly do not know what to do. I created a
>database for myself, no one else uses it. I have selected the "Compact on
>Close" option, but when I go to the location to open it again, I see the
>original file with a large file size and then a file name, "db1.mdb" with the
>smaller, compacted size. This just started happening in the last week,
>otherwise it has always compacted correctly. Any help would be appreciated!
From: MichelleM via AccessMonster.com on 5 May 2010 09:56
I will do that, thank you!

Tom van Stiphout wrote:
>Turn that option off. It was one of those occasional bad ideas coming
>out of the Access development team. Compact when you need to, which is
>usually much less frequently than at every exit.
>
>-Tom.
>Microsoft Access MVP
>
>>This may be a dumb question, but I truly do not know what to do. I created a
>>database for myself, no one else uses it. I have selected the "Compact on
>>Close" option, but when I go to the location to open it again, I see the
>>original file with a large file size and then a file name, "db1.mdb" with the
>>smaller, compacted size. This just started happening in the last week,
>>otherwise it has always compacted correctly. Any help would be appreciated!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access/201005/1

From: John Spencer on 5 May 2010 11:34
Also, the failure to rename db1 to the original file name may indicate that
the compact ran into some corruption problem.

Make a backup of your database and try a manual compact and repair. If it is
successful then great.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

MichelleM via AccessMonster.com wrote:
> I will do that, thank you!
>
> Tom van Stiphout wrote:
>> Turn that option off. It was one of those occasional bad ideas coming
>> out of the Access development team. Compact when you need to, which is
>> usually much less frequently than at every exit.
>>
>> -Tom.
>> Microsoft Access MVP
>>
>>> This may be a dumb question, but I truly do not know what to do. I created a
>>> database for myself, no one else uses it. I have selected the "Compact on
>>> Close" option, but when I go to the location to open it again, I see the
>>> original file with a large file size and then a file name, "db1.mdb" with the
>>> smaller, compacted size. This just started happening in the last week,
>>> otherwise it has always compacted correctly. Any help would be appreciated!
>
From: a a r o n . k e m p f on 6 May 2010 13:11
SQL Server does this automatically.. you should upsize to SQL Server
and lose the training wheels

thanks

-Aaron


On May 5, 6:16 am, "MichelleM via AccessMonster.com" <u44423(a)uwe>
wrote:
> This may be a dumb question, but I truly do not know what to do.  I created a
> database for myself, no one else uses it.  I have selected the "Compact on
> Close" option, but when I go to the location to open it again, I see the
> original file with a large file size and then a file name, "db1.mdb" with the
> smaller, compacted size.  This just started happening in the last week,
> otherwise it has always compacted correctly.  Any help would be appreciated!
>
> --
> Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/access/201005/1

 | 
Pages: 1
Prev: 2 independent criteria in query
Next: Unlock table