Hi Thomas,

The issues behind your bug report were addressed in the transition from
gnucash 1.8 to gnucash 2.0. There were a number of issues with the way
1.8 stored data which were solved in 2.0. Data files created with
previous versions should now be automatically updated when loaded by 2.0
to remove problems like this. (Unfortunately, it also means that such
data files may not be editable / loadable by gnucash 1.8 anymore.)

Please can you test in gnucash 2.0.1-1. Simply upgrade to the latest
version in Debian unstable, load your data file, save it and then retry
to edit the transactions that caused trouble originally.

If you want to retain 1.8 compatibility, copy the file to a new location
before loading it in gnucash 2.0.x

Thanks.

-- 

Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to