On Saturday 19 December 2009, Geert Janssens wrote:
Ok, I think I understand this better now. Thanks for explaining Derek
Yawar.
I agree with the paradigm idea. Indeed in GnuCash you typically work in one
document. That wasn't very clear to me, as I use GnuCash for 3 different
businesses.
Ok, I think I understand this better now. Thanks for explaining Derek Yawar.
I agree with the paradigm idea. Indeed in GnuCash you typically work in one
document. That wasn't very clear to me, as I use GnuCash for 3 different
businesses. But even then I only work on one business at the same
I am about to close https://bugzilla.gnome.org/show_bug.cgi?id=479581 as it is
fairly trivial.
I think the bug is still open because of the log archive it links to:
http://lists.gnucash.org/logs/2007/09/2007-09-26.html#T18:37:32
In short Derek would like to see that GnuCash can never be running
Geert Janssens janssens-ge...@telenet.be writes:
[snip]
P.S. Although I started this discussion, I'm not sure I will be the one to
implement all this, given I don't have the experience (yet). But I would like
to come to a clean design spec anyway as I didn't want Derek's suggestion to
go
On 12/18/09 7:06 AM, Geert Janssens wrote:
[...]
Enforcing a file to be selected from the start, or disallowing any action
if no file is available is one way to deal with this. In case of a db
file
or an sqlite file, all changes are written to the backend immediately, for
the xml file a
