quicken 2009 will not open

Since January 1 - quicken 2009 will not open Uninstalled and reinstalled - will not open Machine is Vista (I tried on my XP and same thing) BUT if I backdate the computer to 2008 - it does work

Even in 2008 the calendar for Feb 2009 has never opened

Quicken Launcher just hangs up and finally give error

Reply to
Laurie
Loading thread data ...

Hi, Laurie.

That's very strange! (But, then, you knew that.)

How about some more details. Like a short description of your computer, exactly which version of Vista (Business w/SP1? - but this is probably not the problem since it also happens with WinXP), and exactly which version of Quicken (Deluxe? R3?). Is this your first use of Quicken or are you a

20-year veteran of Q? How are you "backdating" your computer: by changing the date in the BIOS, or some other way?

How do you start Quicken? By clicking on qw.exe or laurie.qdf? Or on an icon for either of those? Or maybe from a script that might encounter a date problem?

Obviously, I'm clutching at straws, trying to find a loose thread to start unraveling. (Pardon the mixed metaphor.) I've never heard of such a condition and I'm trying to think of what might possibly cause or affect it.

On a side note that probably has nothing to do with this: I've heard that many users of the 30 GB Microsoft Zune (iPod competitor, 30 GB only; other sizes didn't have the problem) were unable to use their machines yesterday - but they are OK today. No clear answer yet, but it may have been because

2008 was a 366-day year and the Zune firmware didn't know how to deal with the Leap Day. And your computer can't open the calendar for February 2009?

RC

Reply to
R. C. White

Found a SORT of fix - a work around really and not happy about having to do it at all. Force the computer date to 12/31/08 - open Quicken Backup a copy of file THEN - Deleted almost 100% of my scheduled transactions - any that were pending February 2009 and later. Under TOOLS Bill and Income Reminder List Edit all transactions you have scheduled beyond January and delete - one by one

Save - backup - and exit Quicken Change computer date back to current and open Quicken - and it did for me.

I am able to start re-adding the scheduled transactions and it seems to be working now - I can even go from Jan 2009 to Feb 2009 in the schedule calendar which was not happening before.

It is not the system I am using, it is not how I open Quicken - it is a bug in Quicken which they seem to not want to admit.

BTW - my first entry took almost 12 hours to post - thus the second entry - the minute I did it both posted - so sorry it you are not happy about it but was not deliberate - just desperate

Reply to
Laurie

It's not a Quicken bug OR a Vista bug (you say you had the same problem with XP) I'm running Vista Ultimate 64 and have had no problem opening Quicken either yesterday or today (Jan. 1 and Jan. 2.)

I can't offer many ideas with the information you've given so far but I can say it's a bug on your computer, something isn't right. Possible a conflict between Quicken and one of your startup programs?

If you could recreate the problem it might be interesting to use MSCONFIG to remove startup programs and see if removing one will fix it?

Reply to
XS11E

I read your post(s) in the Quicken Forums: it was suggested to you there that you check your Scheduled Transaction List ... but you never acknowledged that suggestion.

This is a very silly statement: while there may be a bug; it has not been proven, nor has it been demonstrated to be reproducable.

Intuit is, like most companies, reluctant to proclaim every customer complaint ... a "bug": if you're waiting around for Intuit to "admit" a bug, you're wasting your time. It happens very infrequently ... and it doesn't have any relationship to the fixing of the bug.

When you - or anyone - can demonstrate how to reproduce this problem (I am not having the problem ... and I have taken a fair amount of time trying to reproduce it), then you can expect Intuit to consider it a problem they need to fix.

Desperation won't help solve a problem.

Reply to
John Pollard

Laurie, sounds like you have discovered the problem; several years ago all of us with the newest version of qkn (don't remember which version) who also had scheduled estimated tax payments both fed & state were unable to open qkn on 01/01. I believe it was either a leap year or the year following the leap year. The solution was to change the computer date to 12/31, open qkn, restore backup & delete ALL scheduled estimated tax payments. We could then change the computer date back to the new year & qkn was fine. The difference is that issue was universal & yours seems to be specific to you -- I would consider that you have a scheduled transaction that is causing the problem.

Reply to
PSJ

I'm as OK as anyone with the notion that one user with a problem does not equal a "bug".

But now that I've read THIS post I think blaming this on Laurie, her PC, or her data is inappropriate. Quicken would clearly seem to have a Leap Year Bug if this post about previous incidents is correct.

No user should have to jump through so many hoops to run a program on 1/1.

Doug

Reply to
Doug

Only for a very few users, don't know why but it does not appear to be a Quicken bug.

The very first thing I'd check is for any Logitech devices/software on the PC. I'm a very long time fan of Logitech but their software for Vista doesn't seem to co-exist with Quicken. Disabling any cam/mouse/trackball/etc. software from Logitech might be the first step in finding a solution....

I didn't.

Reply to
XS11E

Which apparently hurt your feelings.

Reply to
Robert not Roberto

However would you arrive at that conclusion? My "feelings" had nothing to do with my comment ... and my feelings couldn't possibly be hurt by the situation described.

You'll want to stay away from that ouija board; it's been giving you bad advice. Goodness knows why you felt obliged to publish it.

Reply to
John Pollard

I posted my comment to push your buttons which obviously worked.

Reply to
Bob L

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.