Performance problem (after One Step Update)?

This one has me. Started I think about Jan 1st. Now, when I jump from register to register, even to an account that has very few transactions, it takes an inordinate amount of time to lose the hours glass indication windows is busy. Especially in my checking account, when I add a new entry, takes about 15-30 seconds for the hour glass to go away, a quick slidebar popup occurs (I think it says 'Refreshing Quicken' or something to that effect, but it is very quick).

For me to accept individually about 8 downloaded transactions took almost 10 minutes!

Especially seems to occur after doing a Quicken One Step Update. I am fine it seems until AFTER I do a download transactions.

Windows XP SP2 with Q2007D.

I just tried validating and Quicken copying the fileset to no avail. I've tried finding and turning off all options that conceivably might have something to do with updates.

Any ideas?

I think the problem is solved.

After thinking about this, I decided to try something. I did confirm the slow up only occured after a ONE STEP UPDATE. So I backed up the entire data directory containing the Quicken fileset and everything else (Q3.dir, qhi.idb, etc. etc. etc.) and then DELETED the ofxlog.dat file, thinking that perhaps this MIGHT have something to do with the performance problem. Why not? Can't hurt according to what I've read and seen recently, and of course, I did have the entire data directory backed up just in case.

Lo and behold, that seems to have done the trick! A new ofxlog.dat file was created after the next download (not unexpected), but it is only 40% of the size of the one I just deleted (perhaps it grows with use). There must have been something that caused the performance problem that somehow was "cured" by getting rid of the old one and having a new one created. Perhaps some entries weren't stored in the old file in the most efficient manner? Who knows??. Not sure what type of correlation there could be, but I ain't one to argue with success.

Posting this in case anyone else has this problem now or in the future.