Submitted by Armando on 2011/01/19 16:34
A few days ago I noticed that my DB went from 280 MB to 440 MB in a bit more than a month. I proceeded to compact the thing but only gained a modest 10MB. I didn't have the time to explorer the mystery further and thought that maybe it was because of the recent research and web clipping (still : 160MB is a LOT of text...) Today, I saw that my DB reached 450MB! Something was definitely wrong... So I tried to compact it again and... Nothing happened. I realised that I had 2 IQ instances running, so I closed one. When I re-compacted, it went down to 275MB. This might be a bug or not. If it's not a bug (e.g. : some data corruption protection) it should probably be documented. P.S.: wonder id there would be other aspects of IQ that are not working as expected when 2 instances are running... ??? If yes, it should be documented.

Comments

MANTIS
1103
Compacting doesn't work when 2 IQ processes (or more) are running  Bugaveragenew
 2011-02-13 14:26

Doesn't the dialog show "error" when compacting with another instance open ? It did here when I tried it...
 
JET database engine (used by IQ) cannot compact a database when another instance is opened. This is one of the very few limitations. Otherwise, JET is an amazing database engine.
 

Armando

2011/02/13 15:47

Permalink

Thanks for testing it. No, here nothing ever happened/happens. (Note that I also run into small problems with some functions / shortcut keys (ctrl-m) not working properly when 2 instances are opened at once. But I can't isolate the cause properly -- sometimes it works, sometimes it doesn't.)