Locking transactions with password before a specific date (Q Mac)

Sasulkey

Are we going to be able to lock transactions before a specific date?

I know there's been talk of it in the past. I'm just hoping Quicken and Intuit will listen. You would think after all the technology and money we spent on these programs that this could be implemented. We can have a car drive by itself, but we can't lock transactions so they are not edited before a specific date with a password??? I just wonder if anyone is actually listening.

I deleted a transaction a couple of days ago from 2009 and that messed up the entire registry. Think how hard it was to find, after days of not knowing when it happened lol.

Using Quicken Classic Deluxe Version 8.0.1 on a 2017 iMac.

jacobs

Are we going to be able to lock transactions before a specific date? I know there's been talk of it in the past…

@Sasulkey There is an Idea post (a feature request) for such functionality which you can view here:

https://community.quicken.com/discussion/7931857/close-books-lock-freeze-old-transactions-with-password-qmac

That request currently has only 9 votes, which means it has not yet been forwarded to the development team for consideration. If you haven't already voted, click the View Post link above and add your vote in the yellow box under the top post. And add a post in that thread about your recent issue, as the developers like to understand actual use cases when they evaluate features to implement.

I'm just hoping Quicken and Intuit will listen.

Just FYI, Intuit has nothing to do with Quicken these days, except in the area of connectivity to financial institutions, which Intuit handles for Quicken under contract. Quicken has been a separate company from former parent Intuit for 9 years.

You would think after all the technology and money we spent on these programs that this could be implemented. We can have a car drive by itself, but we can't lock transactions so they are not edited before a specific date with a password??? I just wonder if anyone is actually listening.

It's not an issue of where anyone is listening, it's an issue of how they prioritize hundreds of feature requests. Quicken is pretty complex software and we all use Quicken differently, so what's important to you might not matter much to me and vice versa. The developer shave to try to assess which of many, many feature requests to tackle and in what order. The Mac development team at Quicken is small and can only tackle a limited number of new/enhanced features each year. They definitely do make steady progress, but it's slower than anyone (including the folks at Quicken) would like.

As I noted above, there was a request for this feature created two years ago, but it has not yet received a lot of votes from fellow Quicken users. If the Idea topic gets more votes, it gets forwarded to the development team for evaluation. They look into whether it is feasible, how much work it would take, and how important they perceive it to be. If/when they put it on their development schedule, the status of the Idea is changed to "Planned", which lets us users know it will definitely be implemented, although we get no clue how far into the future it is on their roadmap.

The issue is not whether it is technologically feasible to create a way to lock transactions prior to a selected date; it's an issue of how this should be prioritized among all the other feature requests clamoring for the development team's time. More votes for Idea posts is one way users can help influence that prioritization.