transaction already being edited in another register
C. Andrews Lavarre
alavarre at gmail.com
Sun May 9 18:21:06 CEST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Regarding
http://tinyurl.com/39mwplx
discussing the subject error, I have found that:
+ The General Ledger shows blank transactions that cannot be deleted
when this error appears. If you try to Delete Splits in the General
Ledger or offending register when it has occurred you then retrigger the
error.
+ However, as suggested in the URL, deleting the transaction immediately
when the autofill fails to perform seems to avoid the error.
But it definitely is a PITA if you have a lot of common transactions to
fill out... :-(
Best regards, Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iJwEAQECAAYFAkvm4PEACgkQOMMPCS4qbIZH7wP+KBBEPoVUo2ht6DOKceGyprVu
blITKaaOovQzzFFheME1oW7VTNqlM7cQXJfO/U2s598Eiaeqxvb49XgVmhBJbcwq
sydXHipioPOHrcSV+TW+smnKTlx3KVTnjY57Ss7oslYkdSSUgB5Xvyk3w4QuIU0D
xCB3EbQB4/QWKcxxoyM=
=GWTz
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list