Robert Merkel <[EMAIL PROTECTED]> wrote:
>I've mostly completed the data-collection part of the transaction
>reports code, and am now figuring out how to implement the formatted
>data output.
>
>I'm going over your mail of a few weeks ago, attempting to figure
>out how to actually implement this
Shae Erisson writes:
> the entire text of this error is:
> [shae@eunuch shae]$ gnucash
> gnucash: bootstrap file is /usr/local/share/gnucash/scm/bootstrap.scm
> gnucash: [W] "failure loading ""/usr/local/share/gnucash/scm/prefs.scm"
> gnucash: [W] "failure loading
> ""/usr/local/share/gnucas
the entire text of this error is:
[shae@eunuch shae]$ gnucash
gnucash: bootstrap file is /usr/local/share/gnucash/scm/bootstrap.scm
gnucash: [W] "failure loading ""/usr/local/share/gnucash/scm/prefs.scm"
gnucash: [W] "failure loading
""/usr/local/share/gnucash/scm/text-export.scm"
ERROR: Unbound v
While transaction locks are important for editing existing
transactions, they don't help in the situation where multiple users
are both adding new transactions to the same account. In that
situation, you do need lock-commit-unlock scenerio. As for getting
notice of changes, a callback from the c
I've mostly completed the data-collection part of the transaction
reports code, and am now figuring out how to implement the formatted
data output.
I'm going over your mail of a few weeks ago, attempting to figure
out how to actually implement this code.
I'd just like some clarifications on a f
