|
Posted by Justan Oldfart on September 15, 2006, 2:14 pm
Please log in for more thread options
> It occurs for me about once a week.
>
> Dick wrote:
>> Happened to me once since I have been using 07. I shut down Internet
>> Explorer and Outlook Express and tried again with positive results.
>>
>>> Hi Neil. I had the same thing happen with Q07 but just once in the
>>> weeks I've been using it and I considered it to be a fluke because I
>>> have a pretty decent processor, XP Pro and 2 gig of ram. I did not
>>> actually have to restart my computer or close any apps, I just closed
>>> Quicken and reopened it and it worked fine. I didn't have that many
>>> other apps open at the time, and Windows Task Manager didn't show a
>>> spike in resources
>>> so I have to wonder if something running in the background like my A/V
>>> software didn't cause a momentary issue.
>>>
>>> Rebooting is very inconvenient, I don't blame you for being frustrated.
>>>
>>> Has anyone else had this problem?
>>>
>>> Shelley
>>> -----------
>>> Shelley Elmblad
>>> About Financial Software
>>> http://financialsoft.about.com
>>>
>>> News Starstream wrote:
>>>> If I have had my computer on for a couple of hours and used a few
>>>> programs
>>>> and then go into Q07, I get the message "Quicken is out of memory and
>>>> cannot
>>>> finish the current task. To release memory, close other applications.
>>>> Try
>>>> restarting Windows or reboot your computer".
>>>>
>>>> I have Windows XP Pro, 512mb memory and no other programs running at the
>>>> same time as Q07. I defragged my hard drive yesterday. I never had this
>>>> problem with my previous Quicken Deluxe programs (e.g. Q05). It will
>>>> work
>>>> if I reboot but what a lame solution!
>>>>
>>>> This is a recurring problem and it quite annoying. What's the point of
>>>> having more bells and whistles if the train won't run?
>>>>
>>>> --
>>>> Neil
It's an acknowledged bug (one of several) with Q07. There is a
knowledge base article about it at Intuit. Easiest fix is to close and
restart Quicken. Hopefully this will be fixed in the first maintenance
update.
|