|
Posted by John on October 7, 2006, 12:25 am
Please log in for more thread options
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:
> 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:
> > 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
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap