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

R52.19 Row Highlighting will not retain shaded.

Michael Vederman

This is not fixed. It was never a problem until I updated to a newer version which appeared in the prior update.

Closing this and saying 'it was fixed in R50' doesn't mean it didn't get reintroduced in a new update. The past is the past, this does not work.

NEVER had a problem until recently.

Reported this in another post for R51.12 that was just closed talking about the past, not the present.

Find more posts tagged with

Windows

Comments

Quicken Kristina

Hello @Michael Vederman,

Thank you for reaching out to the Community and telling us about this issue. I'm sorry to hear you're running into this problem. If I'm understanding correctly, this issue was fixed in R50, but then returned in R51.12? When did you first notice that the issue returned? Could you please provide more detail about what is happening?

Thank you.

BBSCInc

I'm having the same issue. Started when I upgraded to R51.12. Actions | Selecting Row Style = Shaded. Change accounts and it goes to Outlined style.

Quicken Kristina

Hello @BBSCInc,

Thank you for joining the discussion. Was there anything that happened just before the issue started, such as a power surge, power outage, unexpected program or computer shutdown, etc? Do you keep your Quicken file on your C drive or is it on a shared network drive? Is your Quicken file synced with any cloud service, such as One Drive or Dropbox (if it is, you will usually see the service name listed in the file location)?

The simplest way to check your file location, if you have Quicken up and the file open, is to click on File, then look near the bottom of the list, just above where it says Exit. It will list the file locations for the 4 Quicken files you have most recently accessed, with the one you are currently in at the #1 spot.

Is this behavior happening in only one specific account register, multiple account registers, or is this affecting all of your account registers?

Thank you.

Michael Vederman

I've been using Quicken desktop (updated to Classic today) since about 2006.

It's been stable until recent updates which seem to be making the product less stable, it's also on transactions it never did before, start posting them back into the same account or double posting them.

Seems every update creates some new data issue to deal with. If quicken becomes unstable that is terrible news, I am so dependent upon it to manage and track my finances.

In any case, this issue is still present with today's update to Quicken Classic and affects all of my 22 accounts. Only transactions which show a shaded (PREFERRED) row are anything under INVESTING.

It is terribly scary to think that somehow software development and QA testing is starting to suffer in a product so vital to the lives of people. But it feels like there are more bugs in this year's updates that any time in the past 17 years I've been a paying customer.

Quicken Kristina

Thank you for your reply,

Was version R51.12 when you first noticed the issue returned? Do you keep your Quicken file directly on your C drive, or is it on a shared network drive? Is your Quicken file synced to any cloud service (such as OneDrive or Dropbox)?

If you haven't done so already, I suggest that you try validating and/or super validating your data file. Please save a backup file prior to performing these steps.

Validate:

File
Validate and Repair File...
Validate File
Click OK
Close the Data Log
Close Quicken (leave it closed for at least 5 secs)
Reopen Quicken and see if the issue persists.

If the issue persists, proceed to Super Validate. If the issue is resolved after performing validation, then please disregard the instructions to Super Validate.

Super Validate:

File
Hold CTRL + Shift and click Validate and Repair File...
Super Validate File
Click OK
Close the Data Log
Close Quicken (leave it closed for at least 5 secs)
Reopen Quicken and see if the issue persists.

Thank you.