Phyllis, I have noticed that it is important to select the best starting point for your purpose. I would also save the file before starting.
If you start from an account rrgister and select check all, it only checks all the transactions in that register. To check the entire file, start from the Account tree register or the General Ledger. Then it is sometimes easy to miss the prigress bar in the lower right corner of the window. For a large file it could take several minutes, but if it has already run, I think it will silently fail to run a second time. I don't know if there is a way to force it to try again. Finally, it does not check scheduled transactions or other non-transactional data such as business features. From a fellow user, I hope that helps. On Mon, May 13, 2024, 9:41 AM Phyllis Bruce <pobruc...@gmail.com> wrote: > Just when you thought you were done with this….. > > I’m running 4.13 on a windows 10 computer. I have a big problem getting > any reports to run properly but today it is the check and repair function. > No option that I choose gives me a “working” indication. I’m trying to be > proactive before upgrading. Couldn’t find anything in the manual. > > > On May 12, 2024, at 3:30 AM, Chris Green <c...@isbd.net> wrote: > > > > On Sat, May 11, 2024 at 03:49:04PM -0500, Adrien Monteleone wrote: > >>> On 5/11/24 3:08 PM, Chris Green wrote: > >>> So, given that I'm going up just one major release I shouls be OK, but > >>> running "Check & Repair" before doing anything else is a good idea. > > > >> Correct. The Check & Repair should run silently automatically upon first > >> opening your file with 5.5, but it doesn't hurt to do it intentionally. > >> > >> The biggest change I recall between 4 & 5 is the new type-ahead search > >> method for the Description field. I personally prefer the change, but > >> some folks didn't like it by how they use that field and their unique > >> list of existing Descriptions. > >> > >> There is also an issue for some, but not others with respect to > >> registers not auto-filling memos from previous session transactions. > >> (I'm one so affected) Mileage may vary on that one. > >> > >> As always - keep a backup. > >> > >> And since you are not on the last 4.x release on the old machine, I > >> wouldn't go back and forth with the same file. Once you migrate, stick > >> to 5.5 or drop back to 4.8 and stay there until you decide to finally > >> make the upgrade should you notice any problems. > >> > > Thanks Adrien, that's just the sort of information/confirmation I > > wanted. :-) > > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
