I also have this problem on Windows 7, 64bit with both the Bitcoin-Qt and Armory-clients installed not on default locations.
Else it works, but this constant rescanning upon each start make it practically useless for me for "fast" transactions.
For offline wallets it's ok to wait for me.
It would be great if this can be fixed, maybe by checkpointing and a Merkle tree hash upon all successfully validated transactions.
I'm experiencing the same problem. If i close Armory and i run it again it rebuilds the database again. Is my blockchain corrupted? What can i do?
By the way is there a way to change the default .wallet location and run the wallets from another folder?