This sounds like the Pg-database.sql did not import smoothly for some
reason.
Most likely reason is that plpgsql may not be available. To correct this,
you can log in as the db superuser (usually "postgres") and run the command:
create language plpgsql;
Then try to run the db import scripts agai
On 7/26/07, Peter McKenna <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I'm currently using version 1.10. I normally don't print and post vendor
> transactions, just post, but when entering one today I accidently hit 'print
> and post'. Nothing happened for some time and I eventually had to close
> Ledger
Hello,
I've been trying to get ledgersmb-1.2.7 up running and having some
issues. I upgraded my postgresql from 7.4 to 8.2, no issues there. I
had sql-ledger running but ledgersmb looked like a more attractive
choice and I had not entered any data so I just dumped the db and
reinstalled. I g
Hi,
I'm currently using version 1.10. I normally don't print and post vendor
transactions, just post, but when entering one today I accidently hit
'print and post'. Nothing happened for some time and I eventually had to
close Ledger SMB and log in again.
To my absolute horror I found that multiple
On 7/26/07, luxe <[EMAIL PROTECTED]> wrote:
Just one more idea refining the David A. Bandel's point #3. What if
the invoice number be configurable by the user in form that the user
can select several separate fields that will form the final (actual)
invoice number.
The current system provide
Just one more idea refining the David A. Bandel's point #3. What if
the invoice number be configurable by the user in form that the user
can select several separate fields that will form the final (actual)
invoice number.
For example, we have choice of: free text (alphanumeric
non-auto-increment)
