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---
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 messa
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 transac
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 wrote:
> Hello, David.
On 3/15/20 4:36 PM, Christopher Lam wrote:
On Sun, 15 Mar 2020 at 20:31, Eric H. Bowen via gnucash-user
mailto:gnucash-user@gnucash.org>> wrote:
* 14:57:56 WARN qif-parse:parse-date/format: format is
y-d-m
but date is [2020/2/6].
This warning only appears during QIF imports, a
Hello, David. More info in the message I just posted. I do use ISO date
format (-mm-dd) for all of my computer-related workEric
On 3/15/20 4:22 PM, David H wrote:
On Mon, 16 Mar 2020 at 07:10, Frank H. Ellenberger
mailto:frank.h.ellenber...@gmail.com>>
wrote:
> * 15:01:20 WA
On Sun, 15 Mar 2020 at 20:31, Eric H. Bowen via gnucash-user <
gnucash-user@gnucash.org> wrote:
> * 14:57:56 WARN qif-parse:parse-date/format: format is y-d-m
> but date is [2020/2/6].
>
This warning only appears during QIF imports, and shouldn't appear in
regular load/save to/from SQL or XML.
Open the file with a text editor, if sqlite, you’ll see:
"SQLite format 3"
at the beginning of the file, otherwise, you’re looking at a compressed (or
uncompressed) XML.
Regards,
Adrien
> On Mar 15, 2020 w12d75, at 4:33 PM, Adrien Monteleone
> wrote:
>
> sqlite files also have a .gnucash ex
sqlite files also have a .gnucash extension.
Regards,
Adrien
> On Mar 15, 2020 w12d75, at 4:19 PM, David H wrote:
>
> Hi Eric,
>
> You may need to provide further info on this, i.e what version of gnucash
> are you using and on what OS ?
>
> You say your file is saved as xml so I'm a bit surp
On Mon, 16 Mar 2020 at 07:10, Frank H. Ellenberger <
frank.h.ellenber...@gmail.com> wrote:
> > * 15:01:20 WARN 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 tr
Hi Eric,
You may need to provide further info on this, i.e what version of gnucash
are you using and on what OS ?
You say your file is saved as xml so I'm a bit surprised to see sql dbi
related error messages in your trace file. So just to remove all doubt -
your file is definitely xml and has a
Hello Eric,
with the trace file your request looks slightly better. How about your
Gnucash version, selected backend, region ...?
From
Am 15.03.20 um 21:29 schrieb Eric H. Bowen via gnucash-user:
> I still have not been able to repair my "Unable to Save to Database"
> error in GnuCash. I've foun
I still have not been able to repair my "Unable to Save to Database"
error in GnuCash. I've found the gnucash.trace file, which has the error
messages, but so far I haven't been able to find any clue for repairing
a database saved in .xml format. Assistance requested.
Trace file follows:
* 14
13 matches
Mail list logo
