Well folks, Intuit has managed to continue its long history of beta testing on its loyal users. After 6 revisions, Q2009 H/B continues to erratically crash due to corrupted data; corrupted data that appears to have been corrupted by R6. It is a known issue and the Company suggestions it to unistall the program and remove the data (after having made a copy) and then re-install. After this, problem stabilized but cropped up occasionally. Be on the look out for this problem and let me know what your solution is .
Be on the lookout for any software that is worth using that has no bugs ... let me know what your "solution" is.
And while you're at it; please explain how Q2009 could have been causing continued problems since its initial release ... that only appeared in release 6. ["After 6 revisions, Q2009 H/B CONTINUES to erratically crash ....". (emphasis added).]
Your claim of a "known issue" is NOT what is normally considered a "known issue". A known issue is one which users who are not experiencing the issue can reproduce. There are an untold number of claims of alleged software bugs, that are false claims. Can you demonstrate that your alleged "known issue" can be reproduced by others. [I have never seen it in Q2009 RPM, R6; I can not reproduce the "issue" in Q2009. I have never read of any other user who could reproduce the "issue".]
It is possible that you are experiencing a bug ... but your attitude indicates that you care less about solving the problem, than in publishing diatribes.
"John Pollard" wrote in news:h3r4p2$qvo$ snipped-for-privacy@news.eternal-september.org:
I don't know 2009 H/B, period. I use at the moment Q2009 deluxe. In the past, "many" years ago, there were problems with Q data corruption. Maybe yours is a similar problem, and hence the following explanation and work around.
Quicken is basically a database program with many records and fields. Editing these in the course of record keeping may easily cause a problem: When you modify a transaction, the old one is marked as "do not use", and a new one added. Even if I knew exactly how Q does this, it is likely to change between versions, yearly editions and revisions. So it is no use going into more details. The problem is that all those "erasures" and modifications clutter up and eventually confuse the scaffold that the database is built on. Eventually, the computer is going to make an error because of the complexity of the erasures and added data. This is a well-known problem with data bases. The "cure" is "compacting the database - editing out the erasures and simplifying the structure. Q (at least the regular Q, don't know about H/B) does not have a compacting utility. Wat approximates it, though, is the copy utility. Copying the whole database (all files of a set) from within Quicken will compact the database. Then, validating will check for database errors.
When I had problems with corruption, I would quarterly copy the database to a new name. This prevent the difficulties, and was simple.
Again, I don't know whether this is your problem, but it might be worthwhile to try. Be sure to do the validating on a copy of the database, either or both before and after copying.
"Eric J. Holtman" wrote in news:Xns9C4C6784FD294ejhericholtmamcom@216.168.3.30:
I'm just relating (pun intended) how I battled the problem, if indeed it is the same kind of problem. My admitting that I don't know exactly ow Quicken implements its database doesn't mean that I do or do not understand database systems. In fact I think I only have a global understanding, but the way corruption creeps in is what I do understand (I think).
I would encourage you to provide more pertinent help to the OP than I did. In fact a throrough diagnosis of his problems would help everyone.
I'm no one's apologist; sorry you can't come up with a better retort than that. You have defined yourself as one who makes statements you can not defend.
Nor do I offer excuses. Learn how to read, and get your facts straight.
I have read every post in the Live Community, as well as every post in the two previous Quicken "forums", as well as every post in this newsgroup since about year 2000. Another mistaken notion on your part.
Some (any) number of complaints do NOT define a bug ... and it is apparent that you do not understand this.
When you learn how to provide the evidence that a bug exists, by all means post back with the evidence.
Since I am not an Intuit employee or shareholder; you're comments are, by your own defintion (with which I agree) uninformed and ignorant. You have repeatedly made ad hominem claims about me and my posts which are totally false. You have had ample opportunity to provide useful evidence ... but have provided none.
You clearly didn't pay a bit of attention to the original post, or my response to it.
I did not say the op's problem wasn't a bug ... did I? Read my post again.
I also didn't say that there were no bugs in Q2009 or the R6 release of Q2009. Read my post again.
The kb article you quote has no demonstrated relation to the original post in this thread, which claimed that the R6 release corrupted Quicken data.
[If the issue being discussed here had been caused by what Intuit stated they knew was a problem in the article you quote ... Intuit already provided a solution for THAT "known issue". But of course, the issue in the kb article is not what the op claimed was the problem. Obviously beside the point for you ... but not for others who might just be looking for a solution to their problem.]
I have always supposed that you had the limited intelligence necessary to know that your drivel was being captured by Google ... but maybe I was wrong.
Now you've added lying to your incredibly limited repetoire.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.