> Why not just set the "compact on close" option and not worry about it?
...because in a split database situation, backends don't usually get "opened"
in such a way that "compact on close" has any effect, and frontends should
either be .mdes or contain so little data that 'compact on close' won't be
doing much of anything.
(If CompactOnClose is set in the frontend file, it will only effect the fe
file, not the backend.)
HTH,
"DCPan" <(E-Mail Removed)> wrote in message
news:1A0A9A64-9940-4292-B6A9-(E-Mail Removed)...
> Why not just set the "compact on close" option and not worry about it?
>
> "BCP" wrote:
>
>> I am executing DBEngine.CompactDatabase on a database in a VBA module.
>> When
>> the compact finishes the compacted database is a few Mb smaller. If I go
>> into that database a run a compact the compacted database shrinks by more
>> than half.
>>
>> Any guesses why CompactDatabase is failing to compact my database.
>>
>> I look forward to your great help once again - BCP
|