On Tue, 26 Aug 2025 13:29:52 -0400 "David T. via gnucash-user" <[email protected]> wrote:
> I would scan the raw xml to see if there were something obvious, but > I don't even know what I'd be looking for. I am considering exporting > the entire file to CSV and then reimporting into a new file,but > again, if the problem is some form of corruption in the transaction > data, this would just propagate the problem in a new file... > > > I am open to creative suggestions. > > > David T. One option is to split your data file into two parts, A and B. I think you need the xml file to accomplish this trick. Then you load each of those files and see if one or both has the problem. Take the problem file and split it into two parts, say B1 and B2. Backup your data obsessively as you go. The object is to continue this process until the find the group of entries with "the problem". After that you can try to edit it to fix the problem. Liz _______________________________________________ gnucash-user mailing list [email protected] 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.
