Community Discussion: NEW 7/13/21 Prompt to Enter Data File Password when No Password is Assigned

NEW 7/13/21 Prompt to Enter Data File Password when No Password is Assigned

Found at: NEW 7/13/21 Prompt to Enter Data File Password when No Password is Assigned

On July 12 @ 16:00 user DrewJo (not the original poster) makes the following, totally factually unsupported and partially demonstrably false, statement.

"This is not a corrupted file. Corrupted files are inaccessible/contents not readable. This particular problem, according to Quicken support, is the result of a recent update (Windows subscription) pushed to our machines that locked the file with an unknown password and the only resolution is that users have to restore from a back-up made two months (prior to the update in question) presumably or to FTP the *.QDF file to Quicken for an attempt to unlock it."

When someone makes a demonstrably false statement - such as this one, "Corrupted files are inaccessible/contents not readable", they are lying. That statement has NEVER been true. A corrupted file MAY be inaccessible, but a corrupted file is NOT necessarily inaccessible.

Regarding this specific situation: if some non-displayable characters had been inadvertently/incorrectly inserted into the location where a password is stored (no matter how that occurred), that would constitute data corruption. It is NOT necessary that ALL (or even anything more than a small amount of) data in a file be corrupted in order for data corruption to have occurred.

Other than noting the lies and incompetence of such statements as noted above, I also submit that such statements, and the disgusting attitude that underlies them, do NOTHING to get any problem solved ... no matter what company (or product) is the brunt of the nastiness.

[For those that do not know me, I include the following (thoroughly disavowing any notion that any person's "resume" is a blank check to support any claim they make): I spent 48 years designing and writing software. I say that only to support the fact that I know what terms like "corrupted data" refer to - and that I have a lot of experience diagnosing software problems. That does not make me perfect, I do not think of myself as always being right, and nothing I say should be interpreted otherwise.]
Reply to
John Pollard
Loading thread data ...

To clarify: it is not necessary that any data be "unreadable" or "non-displayable" for data/file corruption to exist.

If a Tag value entered by the user in a previously blank Tag field, is placed by the software in the Memo field instead of the Tag field; that would create corrupted data. The Tag field would remain blank, which is valid; and any displayable data is valid in the Memo field - both fields would be "readable" and the data file would be accessible. But the data would corrupted.

Corruption can occur in many ways, including ways not the fault of the software (such as a power outage, or a seemingly minor hard drive glitch). But only certain instances of corruption make a file entirely inaccessible.

Reply to
John Pollard

Sorry, I just noticed that I incorrectly provided the Subject of the Community Discussion, instead of its URL.

The Community Discussion can be found at:

formatting link

Reply to
John Pollard

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.