Donald Allen <donaldcal...@gmail.com> writes:
>> Not a bad idea. Or perhaps it should get run prior to a Save-As?
>
> My preference would be to run it periodically, rather than prior to a
> save-as. An xml file may get improperly structured, as mine did, due
> to problems in gnucash. Even if the bad structure doesn't cause
> trouble immediately, it could do so in later, more correct versions of
> gnucash, perhaps in subtle ways, even if the user never uses the
> database backend. And if Check & Repair can fix the structure, as it
> did in my case, why not use it? It's cheap to run, I don't think users
> will typically do it on their own unless things are obviously broken,
> and if they don't use the database backend, they are unlikely to do a
> save-as.
It would be nice if we stored a version # in the data file, and then we
could run it anytime we updates the version.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warl...@mit.edu PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
