FIND Causes Program to "Crash"

I can't recall anyone else mentioning this; I think if others have had the problem, their numbers are small.

I think you have corrupted data, or a corrupted installation.

For corrupted data, Validate a Quicken Copy of your data: if the Validated Copy doesn't exhibit the behavior, make that your regular file.

For a corrupted install: reinstall. I suggest a new folder for the software, and before installing, removing all folders with Quicken in their name (except your data folder(s), of course).

Thanks John. That's exactly the advice I got directly from Quicken. The odd thing is though that if I reboot the computer when the program fails, it acts normally when rebooted.....for a while, and then it stops working again. So, I don't think that would require a full reinstall. Do you?

I don't have the knowledge to answer your question. As is often the case, I have to deduce answers based on my personal experience, and what I have read from others.

If a reboot seems to solve the problem, I would look for what runs after you reboot.

One thing I would try is to boot in Safe Mode, guaranteeing that NOTHING else but Quicken is running (several times), run Quicken and see if you get the same results.

Given the infrequent reports of your problem, I would bet that it is realated to your particular setup.

[I don't use Q2009 on a regular basis, but I have it installed, and I run it fairly often to try to judge its capabilities and to see if I can reproduce problems reported by others.]

Thanks again John. I'll try your suggestion.

And, I should have said in my previous reply: your Quicken data may be corrupted.

And, if Validate (and Super Validate) can't find the problem ... it is still possible that your data is corrupted.

"Jan Groshan" wrote

How large is your Q fileset? Do any other programs exhibit unusual behavior?

I too have 4 G of ram in XP SP3. (XP sees all the 4 G but only uses a little more than 3 G).

FWIW: I used to have that problem when I asked for "Find All" in earlier versions of Q Deluxe, but not when I asked for just find. Never found a solution for it. With Q 2008 I can now do find all without Q crashing.

Jeff

Not sure what you mean by Q fileset. I was also having a problem with my Outlook 2007, but that seems to be resolved now.

Hi, Jan.

A "Q fileset" is what Quicken calls "a file". Everybody else agrees on the definition of "file", but Intuit's definition of a Quicken "file" includes several related files. The set always includes one with the .qdf extension, but it usually also includes from one to a half-dozen or so with the same filename but with other extensions, such as .qel, .qtx, .qph, .idx, etc.; the composition of the set varies depending on which Quicken features are used by each customer. While Quicken calls the whole group "a file", we often refer to them as a "fileset" to emphasize that Quicken needs the whole group to run properly.

Fileset sizes grow with use; mine currently includes 6 files totaling nearly

40 MB, including 30 MB in my .qdf file. In addition, Quicken creates a full set of backups each week and saves the 5 latest weeks in the \BACKUP subfolder, which it created in my Quicken folder.

Whenever we use Quicken's own tools (Copy, Backup, etc., usually on Quicken's File menu), the whole set is handled automatically as needed. But when we are dealing with Quicken files outside Quicken (such as in Windows' or a third-party's Copy or Backup program), we must remember to include the full fileset. Many users have used Windows Backup to save their .qdf file to a different folder or computer and then have been disappointed to find they also needed those other files in the set - which may no longer be available. :>(

So if you are moving your JanG.qdf file, using tools other than Quicken's, be sure to move the whole JanG.* fileset, including JanG.qel, JanG.qtx, etc., to avoid disappointment later.

RC

In that case, I have a couple of "file sets". They range in size from less than 5 meg to about 13 meg. Compared to yours, that doesn't seem too big.