Q2006: Aborts On Startup

I had the program working on yet another computer. Everything was working fine until I tried to do a Web Connect download from Charter One Bank. After this download aborted I was not able to get my data file to load in Quicken. I called technical support and he had me reinstall Quicken. After reinstalling Quicken I was able to load my data file. We ran a Validate and a Super Validate and there was no data corruption. I was able to use Quicken again. I tried to do a backup which ended with an error (#7097), which I sent to Intuit.. I kept trying to load the file by doulble clicking on the data file and by opening it after getting into Quicken. I got additional error messages (#7157 & 7085). When I tried to send these error reports they would not go and I had to abort the sending in Task Manager.

How can I be using the program with no problem and then get 1 error and the program will not load my data file again? By the way I also tried using the files I had backed up previouslly (prior to the first problem) that worked fine and had no data corruption and they would not load either. Now every time I try to use Quicken with my data file, it says that it is load the data but then stops and I am back at my desktop.

HELP!!!! John Novak

Reply to
John
Loading thread data ...

John--

This sounds suspiciously like a problem I have encountered with Q2004 Premier, versions R3-R5. I've been following this string as I suspect I will finally have to upgrade to Q2007 this year.

One solution that works for me (before the error re-appears) is to copy the data file (I usually will do a 1-1-1965 through 1-1-2010 copy) and then use the copy. (More precisely, have Q rename my datafile, validate, super validate and copy back into my standard file name which I continue to use until the problem re-appears.)

I'm running XP Pro with 1 Gig of RAM and ooodles of harddisk space. The only recent software updates are Window's monthly fixes and McAfee's episodic updates. No recent hardware updates (or except as noted driver updates).

My file QDF file is 47.7 megabytes. Though the problem started around the low 30's.

Below is one of my old emails, annotated to update it

Date: Tues, Dec 6 2005 12:00 am Email: "XXXXXXXX" Groups: alt.comp.software.financial.quicken

"Arnie Goetchius:

I've reported this error several times over the years since I upgraded to Q2004. It started for me with R3 and has continued to the present with Q2004 R5.

If you search this Usergroup, you will find similar errors back to at least Q2002. (I jumped from Q2001 to Q2004, so I cannot speak from experience). But interestingly, I cannot recall anyone complaining about memory read errors in Q2005 or Q2006. I have seen messages in this Usergroup stating that the newer versions just stopped. Maybe Intuit eliminated the error message? THAT SEEMS TO BE CONSISTENT WITH YOUR 2007 EXPERIENCE.

I would doubt that it is a physical memory issue. Do you have this problem with other software? I don't, and I may have a dozen applications open at any one time. FOR THE RECORD, THE PROBLEM OCCURS WHEN QUICKEN IS THE ONLY PROGRAM RUNNING OR WHEN SEVERAL PROGRAMS ARE OPEN.

I think it is a software bug that is harmless until you have either lots of data (I started using one of the early DOS versions, my transaction history goes back to 1990, and my investment history goes back to 1967 (a gift of stock which I still own), lots of accounts (some 100+, though most are closed), lots of investments over the years (but I usually stop keeping current price history on stuff I've dumped), or something similar which causes an internal table to expand to a size greater than the software engineer thought was necessary.

I WOULD GUESS THAT THE REASON YOU GET A DATAFILE TO WORK ON SOME COMPUTERS BUT NOT OTHERS IS PROBABLY RELATED TO MY EXPERIENCE WITH HAVING QUICKEN COPY MY DATAFILE AND THEN USE THE COPY -- THE COPY ROUTINE RE-SETS SOME VALUE WHICH CHANGES EVERYTIME WE OPEN THE DATAFILE. THE ONLY WAY TO VERIFY THIS WOULD PROBABLY BE TO CLOSE A DATAFILE SET, MAKE A COPY USING WINDOWS. RE-OPEN THE OLD DATAFILES IN QUICKEN. CHANGE 1 CHARACTER IN SOME RECORD. THEN CHANGE THE CHARACTER BACK. CLOSE QUICKEN, AND THEN DO A BYTE LEVEL COMPARE. I HAVE A HUNCH THERE WILL BE DIFFERENCES.

That's all I'm saying. ...... BUT IF YOU DO FIND A CURE, PLEASE POST IT.

-dll

John wrote:

Reply to
dllapides

I am using WIndows XP Professional and also have lots of hard drive space. If it is in fact a software bug why won't Intuit acknowledge it. If you call them with a large data file, they immediately tell you reduce the size considerably.

I am confused by the fact that it was working fine until I ded a web connect download, then the problems started. The file would not open. Why did reinstalling the software fix the problem temporarily? There must be something written to the registry or to some hidden file that prohibits the large file from loading while allowing smaller files to load even though the larger file is not corrupted. Someone must know what is causing this problem!!!

If the problem is an internal data file that is too small, why doesn't Intuit fix it? I can't believe that it is in their best interest to have unhappy customers and a product that is buggy!!

Thanks, John Novak

dllapides wrote:

Reply to
John

John--

I got out of the software industry in 1975, so I am obsolete. But one of my projects back then was to figure out why a print routine in a statistical package "bombed" whenever the number of pages exceeded something like 850 pages (that big 132 column paper). The software module was probably 2,000 punch cards long, in a mixture of COBOL and assembly language. Needless to say, it was a very difficult bug to track down, and you had to take over a mainframe to try fixes.

But in those days, we all could read and write assembly language and go though it line by line until we found the error. Needless, to say a routine that worked on 750 pages of printout but not 850 pages had a very obscure bug.

My point is we had a fighting chance. We had a good idea where the problem was and had tools that let us monitor the situation and dealt with static, lock step code. We also had a management that wanted the bug fixed because it affected a lot of important folks in the organization.

The guys and gals at Intuit if they were to chime in would probably tell us that Quicken is 1,000,000 lines long of some process driven (i.e., mouse click activated) programming language and the problem could literally be anywhere. And I'll hazard a guess that you are not willing to share with them a live data file that they could use to duplicate the problems. I know I would not.

But why do the help line folks give you mis-information? I suspect most of them are reading from a script. The folks who wrote the script are a committee of marketing folks who want customers to feel like Intuit is being helpful. (The lawyers sure are not going to let them say "We don't have a clue why it doesn't work.")

Is it fixable? Unless Intuit wants to incur the cost of re-writing Quicken from scratch, I think it will pure happenstance that this gets fixed.

PS-- I tried my 1 cent change, and then change back, found my ancient PC Magazine COMPARE.COM DOS utility from 3 or 4 computers ago. Yep, the QDF file and the almost duplicate QDF file show differences at the byte level. This gives credence to my thought that the database itself constantly changes whih results in the episodic nature of the problem.

Where do we go? Heck if I know. With my historical data, converting to MS Money would not be much fun.

-dll

Reply to
dllapides

So my only options are to stop using Quicken or to delete the majority of my historical data, right? The most frustrating part is that Intuit's technical support will not even entertain the fact that there is a problem! If they did, maybe some of the users having this problem would work with them during beta testing to fix the problem. But if you won't even acknowledge that there is a problem it will never get fixed. Their solution is always to get rid of all but a coule of years of data. Not only do I not want to do this, I am sure that if I broke down and did it they would solve the problem and my data would be gone. What options do I have? Who can communicate with Intuit to start a dialog to get the problem fixed?

Thanks, John Novak

dllapides wrote:

Reply to
John

Antoher thing that I do not understand is many times Quicken will abort and generate an error code like 7097. When I talk to the technical support staff they have no idea what this means! Where is this error code coming from? Is it being created through devine intervention? Why would Intuit generate the error code but then have absolutely no idea what it means. I am completely confused and frustrated!!!!!

Thanks, John Novak

John wrote:

Reply to
John

John:

Quicken 2007 has a 60-day money-back guarantee.

Would you consider picking up a copy of Home & Business, installing it, and seeing if H&B 2007 will successfully convert your 2006 file, and open it?

I know that in my situation Q2007 would open files that would crash Q2006.

There are other problems with Q2007, but it seems like your most immediate concern is to have access to your Q2006 file.

Bob

"John" wrote in message news: snipped-for-privacy@m7g2000cwm.googlegroups.com... So my only options are to stop using Quicken or to delete the majority of my historical data, right? The most frustrating part is that Intuit's technical support will not even entertain the fact that there is a problem! If they did, maybe some of the users having this problem would work with them during beta testing to fix the problem. But if you won't even acknowledge that there is a problem it will never get fixed. Their solution is always to get rid of all but a coule of years of data. Not only do I not want to do this, I am sure that if I broke down and did it they would solve the problem and my data would be gone. What options do I have? Who can communicate with Intuit to start a dialog to get the problem fixed?

Reply to
Bob Wang

John,

did you try what I suggested back in September? It has always worked for me. Delete the temporary directory

"c:\documents and settings\all users\application data\intuit\quicken"

Then do a Reinstall, and select the "repair" option.

If you haven't done it, it should be worth a try.

Regards, Jim

222 12356 body John wrote:

John,

did you try what I suggested back in September? It has always worked for me. Delete the temporary directory

"c:\documents and settings\all users\application data\intuit\quicken"

Then do a Reinstall, and select the "repair" option.

If you haven't done it, it should be worth a try.

Regards, Jim

Reply to
Jim Henry

Jim:

I finally got around to trying your suggestion and I can't believe it. IT WORKED!!! I have tried it on three of the computers that no longer work and it has worked on ALL of them. I can't thank you enough for you tip! Since this works, does it give us any indication of what the problem is? Is it something that Intuit could use to fix the problem? All of my data is intact and just how I left it before the last crash. There does not seem to be any data corruption! If I upgrade to Quicken

2007 will the same thing happen and will your fix work? I guess I should first ask if it is even wise to upgrade to Qucken 2007?

Again, Jim, thanks a million!

John Novak

Jim Henry wrote:

Reply to
John

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.