Validation should specify what it changed [+14 Merged Votes]

Rocket you are absolutely correct.

The detail provided is insufficient to verify or correct the errors encountered.

I remember a report I got several years ago that listed 10 or so error messages. Each message was identical with no way to know what record each referred to.

I just did a File Validation and report said that a Category had been deleted and I should check my Categories List for the missing one. No offense, but "Come on, man". With a Category list as long as it is (>100) this is not really a practical suggestion.

I would suggest that the report tell the user which Category(ies) were deleted by name. There might be times when the name is the corrupted field, but I'm guessing that would be the fewer of the number. Most times it would be possible?
Best, Jim

I agree it's dumb that it doesn't list the deleted categories. I, too, have a ton of categories. My work-around is that when I see that message, I print the category list to a file from both the current file and a recovered file. Then I use a text compare utility (Beyond Compare) to see what's changed. It works, but it's a hassle.

An even better solution than simply telling us what category was deleted would be to assign all those deleted category transactions to a new category during the validate process -- ideally "[deleted category]_new". Then we'd know which transactions were affected.

Agree with above comments. In fact, rather than deleting a category, please just tell me what error quicken thinks it found and let me decide how to fix the error. This is very frustrating to try to fix out what Quicken did to "fix" my file. If indeed a fix was required at all.

davezechnich said:

Agree with above comments. In fact, rather than deleting a category, please just tell me what error quicken thinks it found and let me decide how to fix the error. This is very frustrating to try to fix out what Quicken did to "fix" my file. If indeed a fix was required at all.

It is highly doubtful that they would ever put in such an option.  A database like Quicken's is going to have all kinds of cross referencing and such.  The purpose of Validate and Repair is to bring the database back to a "consistent state".  The user doesn't even have any idea of what that is, let alone direct how to fix things.

I ran Validate and Repair. Validation gives the message: "Repaired your data file by removing a damaged category. Please check your category list for missing categories by going to Tools>Category List."

That's a pain. Why can't it simply list the categories it removes?

I whole heartedly agree, but I'm of the belief we have to be careful what we wish for. Look at the great ideas for Mobile and Web, then Schwab. Quicken may open a whole new can of worms....again!

Boatnmaniac said:

TTSguy said:

I whole heartedly agree, but I'm of the belief we have to be careful what we wish for. Look at the great ideas for Mobile and Web, then Schwab. Quicken may open a whole new can of worms....again!

FYI:  The current Schwab connection and download issues situation was inflicted by Schwab.  They changed their connection method and safety protocols and messed it up royally.

At this point I don't put the all on Schwab.  It is quite evident that Schwab worked with Quicken Inc and Intuit and many more financial institutions to start changing over to this new process.  I personally think the new process stinks in comparison to OFX/Direct Connect, but in reference to secure all the "aggregators" it is a good move.  And just look at what Quicken Inc has been putting out, at least on the surface they have been broadcasting that they believe in this new system.

So, I wouldn't put this all on Schwab.  The bottom line is that the world is going to change whether we like the changes or not, or if they are actually better or not.

I know a lot of people believe in "If ain't broke don't fix it.", but this statement ignore two main facts.  One is that you need to change things just to maintain them.  And two, the world isn't going to allow you not to change.

As such I can certainly see @TTSguy's fear of changing anything because it seems like whatever the Quicken Windows developers touch, they break, that isn't going to stop them from making changes and you might as well lobby for the changes that you really want.

And as for the blaming of these problems on Schwab I would say that this was definitely a "group effort".  No matter the pain to change the connections from FDS to QCS, and the change from Express Web Connect to Express Web Connect + for both Capital One and Schwab, I have heard nothing, but praise and optimism for these conversion from Quicken Inc.  They aren't the "victim" they are active partners in this.

And here is something else to chew on.  Scan this forum for Capital One and Schwab Quicken Mac problems.  They are there, but they are far less frequently having problems even when you consider there are less Mac users than Windows users.  And I have seen where the Quicken Mac users are shy to complain.

this might be fixed in R38.30 build 27.138.30
! ran a Validate this morning. Results had the 'standard' error found but then a new section listing two transactions (I xx out the account names and amounts). reviewing these accounts showed the Transaction's category was blank. I deleted and recreated them


[Sat Feb 26 08:57:05 2022]
QDF:
Validating your data.
Quicken found a damaged scheduled reminder and removed it. Please check your scheduled reminders by going to Tools>Manage Bills and Income Reminders.

[Sat Feb 26 08:57:29 2022]
------------------------------------------------------------
The following transaction(s) involving transfers appear to be damaged.
You should delete them and recreate as appropriate.

Account XXXXX: 3/5/2022 XXXX $$.$$

Account XXXXX: 3/16/2022 XXXXX $$.$$