I am in favor of a flag forced_close.
Maybe with possiblity to insert comment in ap.intnotes,ar.intnotes
Thanks,
Herman
2008/4/10, Chris Travers <[EMAIL PROTECTED]>:
>
> One of the issues that people can run into in importing data from
> other accounting systems is that poorly designed systems ca
One of the issues that people can run into in importing data from
other accounting systems is that poorly designed systems can have
internally inconsistent data within them. In some of these cases,
generally accepted accounting principles prevent adjusting the data in
order to resolve these errors
Quoting Chris Travers <[EMAIL PROTECTED]>:
The major drawback is that anything which hits this field needs to join
> against the (much-larger) acc_trans table. This means that there is a
> performance cost in large installations where these fields are used (AP/AP
> Reports, payment handling, etc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 2 Apr 2008 13:56:28 -0700
"Chris Travers" <[EMAIL PROTECTED]> wrote:
> The major drawback is that anything which hits this field needs to
> join against the (much-larger) acc_trans table. This means that
> there is a performance cost in large
Hi all;
One of the problems which occasionally happens for people trying to work
with LSMB is that summary information can get out of date. This is expected
to be a further issue for SQL-Ledger 2.8 migrations because of specifics on
how that information is calculated.
It seems to me that the bes
