Kaffis Mark V wrote:
What kind of transactions are you importing? It seems likely (to me, at least) that this feature involves interacting with external APIs, like other companies' websites (your bank, your credit card, etc), and that keeping that feature operational involves ongoing coding work to update the Quicken product itself to maintain compatability as others change their APIs.
Thus, eventually, you stop supporting an older product with upgrades to retain compatability, and one of two things happens: compatability steadily declines as those other companies make changes to their APIs, or you code a shutoff to that feature so you don't get a bunch of confused support calls demanding to know why imports with company X work fine, but they're now broken with company Y.
I have no idea whether this musing will change the way you look at this situation (nor do I have a dog in the race, so to speak), but I hope it may have at least proven informative, or presented an angle you hadn't considered.
This version of Quicken only allows imports of certain file types, all of which are proprietary to them. As a programmer who has to code conversion routines for database and product upgrades, I will say that what you laid out is the lazy man's excuse. I could see releasing a patch that ensures compatibility of what you're trying to import and denying it if the data supplied by the 3rd party is no longer in a valid format. But to shut the feature off altogether is ridiculous no matter how you spin it.