Quicken 2007 - Out of memory when doing update = corrupted data file

Posted by Todd Last on September 30, 2006, 11:12 pm

Please log in for more thread options

I upgraded from Quicken 2006 Premiere to 2007 and ever since upgrading,
I am consistently getting "out of memory" messages when I do the
electronic update (on a machine running XP Pro and 1GB Ram).

The result is this corrupts my data file - discovered by doing file
validation - last time it tossed out 168 transactions.

Has anyone had this problem or know of a solution?
I'm thinking the only way out of this is to build a new data file from
scratch.

Posted by jimnl69 on October 3, 2006, 2:10 pm

Please log in for more thread options

Todd Last wrote:

> I upgraded from Quicken 2006 Premiere to 2007 and ever since upgrading,

> I am consistently getting "out of memory" messages when I do the

> electronic update (on a machine running XP Pro and 1GB Ram).

> The result is this corrupts my data file - discovered by doing file

> validation - last time it tossed out 168 transactions.

> Has anyone had this problem or know of a solution?

> I'm thinking the only way out of this is to build a new data file from

> scratch.

I too am having the same issue. I'm costantly getting our of memory
errors on my 1.5GB machine that has 1.1GB free when this occurs. It
also occasionally wants to do transfers from a month or 2 ago as if
they were never done.

Posted by Mark Krubsack on October 3, 2006, 2:57 pm

Please log in for more thread options

Same here with 2 Gigs of ram. Quicken likes to be the only application
running, or at least the first one executed. If I execute IE before
Quicken 2007, I will always get the out of memory error.

On 3 Oct 2006 11:10:51 -0700, jimnl69@hotmail.com wrote:

>Todd Last wrote:

>> I upgraded from Quicken 2006 Premiere to 2007 and ever since upgrading,

>> I am consistently getting "out of memory" messages when I do the

>> electronic update (on a machine running XP Pro and 1GB Ram).

>> The result is this corrupts my data file - discovered by doing file

>> validation - last time it tossed out 168 transactions.

>> Has anyone had this problem or know of a solution?

>> I'm thinking the only way out of this is to build a new data file from

>> scratch.

>I too am having the same issue. I'm costantly getting our of memory

>errors on my 1.5GB machine that has 1.1GB free when this occurs. It

>also occasionally wants to do transfers from a month or 2 ago as if

>they were never done.