Did you completely close the client when swapping wallets ?
As far as I understand, it should work. Each wallet keeps a pointer to the last block it knows about. During the application initialization, the last block in the blockchain file is compared to what the wallet is aware of, and a partial rescan is performed if needed.
If I swap my wallet with an older copy, it takes a bit longer than usual to start, but the new transactions to/from my wallet are visible right away. (Not tested with two completely different wallets though)
There was a thread about a similar problem recently, so maybe there's an issue somehow.
Topic: Pitfall using the same block chain data with different wallets (Read 1307 times)
Or you could just use the -rescan command line option which will go through the block chain and find your missing transactions without having to re-download the block chain.
Code:
-rescan Rescan the block chain for missing wallet transactions
yes, this is why the bitcoin wiki recommend that you delete blockindex.dat file each time you switch wallet
I use multiple wallet.dat files with the same block chain data. (By "block chain data" I mean all the data in the .bitcoin directory other than the wallet.) Apparently, this method does not work perfectly with the standard client. I tried sending BTC from one wallet to another, by switching the wallet file, and the BTC never showed up in the new wallet. However, it showed up on block explorer, so I knew the transaction was successful. So I deleted the block chain data and downloaded it again, and then the BTC showed up in the new wallet.
Lesson learned: If you use more than one wallet, it appears to be necessary to keep block chain data separately for each wallet, otherwise your transactions might not show up.
Lesson learned: If you use more than one wallet, it appears to be necessary to keep block chain data separately for each wallet, otherwise your transactions might not show up.
Jump to: