Hi Mark,
A small possible "bug." As you are aware, I was away on vacation earlier this week and unable to get to AI. However! I wasn't going to let the swoon of the market go unnoticed, so I "guesstimated" as the market was making new lows. Now home on Saturday, I'm going to update AI with my guesstimates. Rather than just enter the transactions as buys, I've been loading the end prices from 17 September, the day I made the purchases to force AI to give a BUY signal which it would have done had I been home!
Here's the 'bug' - when manually updating prices in multiple-security portfolios, it defaults to the current date. In each case I over-rode the default from the 20th to the 17th. Yet, when all the updated prices post, in the transaction line they're posting with the current date of 20 September. So, when I go to enter the buy transaction on the 17th, the software stops the entry due to the presumed buy being earlier than the later, though incorrect price update transaction. So I'm dating the buy to match the 20th.
What would be nice is if the multiple price update would not only post correctly, but carry forward the first date that you enter as you enter each price, rather than having to change the date each time.
Thanks for your consideration. Version 3.0, SP6
Best,
AIMster
AI
