An interesting error

2.) Try creating a new test file with enough content to repeat the problem, and see if the problem occurs there. If not, you probably have corruption in your data. If so, either revert to a backup, or try Validating a Quicken Copy of your data. 3.) Your Quicken installation might be corrupted; try a reinstall.

I can't give you a definitive answer. I can just note that I use Outlook Express to read newsgroup posts, and you're correct, I do see Andrew's image when I use OE.

And I don't see that image when I view Andrew's post using Google.

Possibly Google is intentionally conserving some server space by not saving images.

Bad guess Andrew.

As fruitless as I expect it to be, I will attempt some small clarifications.

First: I did not attempt to "justify" the message, I made an educated guess at the reason why the message did not contain more specific detail.

If the handling of the message was pure laziness on Intuit's part, then sure, that's not justified.

There are certainly hundreds of possible OFX errors that could be created by the financial institutions (only three of which were listed); it's not clear what the business case is for making the effort to tell Quicken users the specifics of each of those errors that the fi created. [Though I personally would like to know ... all other things being equal.]

And that's assuming there are no other circumstances involved that would add to the difficulty of identifying the specifics to the user.

Here it seems clear there were other circumstances involved: as my first post demonstrated, the "OLB" error message could be caused by reasons having nothing to do with invalid OFX data. The other two causes of the OLB error message are corrupted Quicken data, and a corrupted Quicken installation. By singling out only one of the three causes for the error OLB message, you have made the potential problem of providing a more accurate error message seem much simpler than it probably is.

When one error message is covering several unrelated errors, it's not uncommon that the effort involved to provide an exact error message for each of the errors is economically infeasible.

My guess didn't come from lack of experience; it came from lack of knowledge of the specifics of this situation. Without knowing what the Quicken programmers know, it's not possible to judge conclusively ... so, I guessed. I'm not troubled if other's guesses are different than mine.

This is a discussion with little value to me, and I think, to anyone else here. So I'm not likely to continue it; you're welcome to the last word.