[GNC] How to fix "Unable to Save to Database" error - Second Request

[Eric H. Bowen]

Well, if it's that simple then just hit me over the head with a wet fish 
and say "D'oh!"

I have re-saved the file. Waiting to get some fresh transactions from 
the checking account to import in order to see if that does the trick. 
Should have some in the morning. Fingers crossed. Thanks, all----Eric.

On 3/15/20 10:26 PM, John Ralls wrote:
> You're using a SQLite3 database, not and XML file, and SQLIte3 thinks that its file has gotten corrupted. If you have backups you should make sure that the one or two from just ´before the first time you encountered the error are safe and available. If you don't have backups then this is a message from your deity to start keeping regular ones.
>
> I think the simplest fix is to re-save to a new file using File>Save As... I suggest doing it twice, one XML and the other SQLite3. You pick which one with the list box on the top of the Save As dialog box.
>
> Regards,
> John Ralls
>
>
>> On Mar 15, 2020, at 4:53 PM, Eric H. Bowen via gnucash-user <gnucash-user at gnucash.org> wrote:
>>
>> I'm seeing the error on all three operating systems, although it first appeared on the Windows 10 computer. The pop-up error message does appear only when importing transactions, and only from one specific account (my personal checking account) at that, and since it seemed as though the transaction records were not affected I put up with it for several months as just a nuisance. However, recently I've been trying to reconcile a loan account for a vehicle which was totaled and paid off by insurance, and when I try to balance the liability of the loan off against the asset for the value of the vehicle it seems to post properly for that session...but when I restart Gnucash for the next session, the amount has moved back to "Imbalance". A couple of other transactions are doing this as well, but the auto payoff is the big'un. I want to get the known error taken care of first, and then when the imports are back to working properly I want to see if I'm still having problems balancing out these transactions and, if I do, I'll post a separate request to the list----Eric.
>>
>> On 3/15/20 6:30 PM, David H wrote:
>>> Hi Eric,
>>>
>>> Yep saw that.  What OS are you seeing the error on, or is it on all of them ? Just saw your other post, so you are getting this when trying to import transactions NOT when saving your Gnucash data file.
>>>
>>> Cheers David.
>>>
>>>
>>> On Mon, 16 Mar 2020 at 09:19, Eric H. Bowen <eric at ehbowen.net <mailto:eric at ehbowen.net>> wrote:
>>>
>>>     Hello, David. More info in the message I just posted. I do use ISO
>>>     date format (yyyy-mm-dd) for all of my computer-related work----Eric
>>>
>>>
>>>     On 3/15/20 4:22 PM, David H wrote:
>>>>
>>>>     On Mon, 16 Mar 2020 at 07:10, Frank H. Ellenberger
>>>>     <frank.h.ellenberger at gmail.com
>>>>     <mailto:frank.h.ellenberger at gmail.com>> wrote:
>>>>
>>>>         > * 15:01:20 WARN <gnc.scm> qif-parse:parse-date/format:
>>>>         format is y-d-m
>>>>         > but date is [2020/2/6].
>>>>
>>>>         That date is in the future. It seems, somebody changed the
>>>>         date format
>>>>         (order of day and month).
>>>>
>>>>     Hmm transaction dates can be in the future, this looks like 6th
>>>>     Feb 2020 to me in ccyy-m-d format ?
>>>>
>>>>     Cheers David.
>>>>
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at gnucash.org
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.