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; } } }

Corruption of check number field in previously posted transactions

tjc74

For transactions entered through an iPhone app, I enter a check number of "iPhone"
Recently, I've noticed that some previously posted transactions (but not most) have the last few characters changed to bizarre accented foreign language characters. The change is consistent in that each change is the same and I can easily fix it with search and replace. This has happened a number of times. I'm running Quicken Deluxe 2020 for Windows. This was an upgrade from 2017.

Find more posts tagged with

Comments

tjc74

The corruption is from "iPhone" to "iPhoúÿÿÿ" and includes transactions reconciled as much as a year ago. The comment fields of these transactions are similar but not identical.

tjc74

The corruption occurs during the update process.

UKR

If you haven't rebooted Windows since you installed the latest software update, please do so now and then try Quicken again.

Still not working?

Let's start with some "Troubleshooting 101" to ensure the Quicken software is installed and updated properly and that your data file is in good working order.
Please perform all the steps in this document in the order specified:
Troubleshooting 101 - Fixing Software Installation and Data File Problems

Kevin W J

I am seeing a similar thing, but only in a monthly scheduled credit transaction. Instead of SvChg, it is displayed as SvChúÿÿÿ. I can select SvChg from the dropdown list and save the transaction to fix it, but sometimes it comes back later. It is only happening to transactions from the last few months.

[Deleted User]

This is a bug that has been around since Quicken rolled out Mobile & Web. It occurs on any custom NUM item but not all. I have found in my accounts it randomly occurs on deposit transactions. It never happens on the standard NUM items.

It doesn't seem to cause any real issue, except maybe being annoying.