client?
Cypherdoc,
Be careful running two clients that use the same keys. Weird things can happen. Armory should be robust to most of it, but I'll be interested to hear if that's really true. Satoshi client has a habit of getting confused, and locking inputs based on transactions that aren't actually valid (because you sent a tx, and then satoshi client tried to spend the same outputs before it got the update, locked the outputs, and then gets stuck). I don't know how multibit is, in this regard...
If that 0.0001 is in the blockchain, Armory should find it. However, in some places where values are displayed, the values might be truncated (but that should be big enough...). Also, sometimes you just have to close the wallet properties and reopen it, in order for the data to be displayed correctly.
The thing to do after importing, is to go into the wallet properties and double-click on the address. It will show you all the transactions that address has ever seen. If it shows nothing, then check blockexplorer or blockchain.info for that address. I've never seen any of those online services be out of sync with what Armory says. But that doesn't mean it can't happen... (please let me know if it is)
I highly recommend that you wait for the other client to receive the transactions of the first client, before attempting to do more transactions. They should have no problem, as long as you give them time to have the latest blockchain data before constructing new transactions in either one.