nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Minor problems with Tags corrected"

Pilotbum

I frequently run a file validation and lately on a daily basis I have got the "Minor problems with Tags corrected" message. If I run a subsequent validation there are no errors. But if I run a validation the following day, regardless of tag usage I get the same "Minor problems with Tags corrected" message. It doesn't specify if it is a particular tag, the tag database, or something larger. Nonetheless, I'd like to correct the problem if possible so it will go away. Super Validate has not helped.

Find more posts tagged with

Windows

Comments

Chris_QPW

About all you can do is upvote this suggestion because Validate doesn’t provide enough information to fix problems like this:
https://community.quicken.com/discussion/7880500/validation-should-specify-what-it-changed-32-merged-votes/p1

Well, actually there is one more thing that can be tried, but it can be painful these days. If you use the “Copy/Template” option it does a record by record copy that and sometimes clean up problems. The downside of it these days is that it disconnects all online services and you have to reconnect them to continue using that data file.

Pilotbum

Chris,

First, thanks for what you do on this forum. I'm rather certain you've always helped me far more than any Quicken technical support employees. Your suggestions have always fixed things where theirs did not.

That said, I have taken your advice and created the copy of my data file. From there my strategy was to keep both files updated but I never re-connected the copied file to my financial institutions online; I kept using the original file. Then I was going to validate each file at the same time and see what happens when the original file give me the "minor problems with tags corrected" message. Well... ever since I created the first copy of the file, the original (source) file has no longer had this errors message. Best I can tell, just copying the file fixed the problem.

Can you think of any explanation for that?

Thanks,

Randy

Chris_QPW

Hmm, one wouldn't think making a copy would change anything in the original, but one can't also deny something must have changed. It is certainly a new one on me.

Pilotbum

Still no more errors...

Nonetheless, thank you.