sql-ledger-users

Missing clauses....

[Paul S. <ps...@co...>]

First off, thanks to everyone who has made SQL-Ledger possible.  Very 
nice code set....

We are considering incorporating the SQL-Ledger accounting system into 
our Applicant Tracking System (manages resumes, contacts, jobs and what 
not).  We are very interested in the multiple payments feature slated 
for 1.8.   Hopefully, we can help at some point...


Anyhow, after using SQL-Leder for a while, I've noticed that my Postgres 
log file is filling up with the following and I wonder if it was 
something I have set incorrectly...



NOTICE:  Adding missing FROM-clause entry for table "customertax"
NOTICE:  Adding missing FROM-clause entry for table "partstax"
NOTICE:  Adding missing FROM-clause entry for table "partstax"
NOTICE:  Adding missing FROM-clause entry for table "customertax"
NOTICE:  Adding missing FROM-clause entry for table "acc_trans"
NOTICE:  Adding missing FROM-clause entry for table "acc_trans"
NOTICE:  Adding missing FROM-clause entry for table "acc_trans"
NOTICE:  Adding missing FROM-clause entry for table "acc_trans"



Regards,

-paul

Re: Missing clauses....

[Dieter S. <dsi...@sq...>]

Nothing to worry about.

There are a few queries which have no FROM clause and the server adds 
the tables. I'll take care of this in the next release.


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========

On Tue, 25 Sep 2001, Paul Stavrides wrote:

> 
> First off, thanks to everyone who has made SQL-Ledger possible.  Very 
> nice code set....
> 
> We are considering incorporating the SQL-Ledger accounting system into 
> our Applicant Tracking System (manages resumes, contacts, jobs and what 
> not).  We are very interested in the multiple payments feature slated 
> for 1.8.   Hopefully, we can help at some point...
> 
> 
> Anyhow, after using SQL-Leder for a while, I've noticed that my Postgres 
> log file is filling up with the following and I wonder if it was 
> something I have set incorrectly...
> 
> 
> 
> NOTICE:  Adding missing FROM-clause entry for table "customertax"
> NOTICE:  Adding missing FROM-clause entry for table "partstax"
> NOTICE:  Adding missing FROM-clause entry for table "partstax"
> NOTICE:  Adding missing FROM-clause entry for table "customertax"
> NOTICE:  Adding missing FROM-clause entry for table "acc_trans"
> NOTICE:  Adding missing FROM-clause entry for table "acc_trans"
> NOTICE:  Adding missing FROM-clause entry for table "acc_trans"
> NOTICE:  Adding missing FROM-clause entry for table "acc_trans"
> 
> 
> 
> Regards,
> 
> -paul
> 
> 
> 

Re: Invoices

[Brian J. <bjo...@je...>]

In regards to some of the recent discussion about invoices ...

As mentioned, saving a copy of the invoice on the hard drive and maintaining
a link to the invoice file within sql-ledger would be great for record
keeping.

Also, a method to produce a draft invoice for review and then go back and
edit it prior to posting it in the accounts receivable would be great.  We
routinely have the project leader review invoices (and suggest
wording/amount modifications) prior to mailing them.

The ability to make a cron job to email invoice drafts to project leaders
once a month would be great too.

Suggestion: Using SAX->XML->FOP for formatted printing

[Jeff K. <jt...@ad...>]

I came across this article today that would offer one possible path for
SQL ledger to offer the formatted printing features that are currently
being discussed.

http://www.xml.com/pub/a/2001/09/19/sax-non-xml-data.html

I found it interesting because the subject discussed would be something
that could be grafted on top of SQL ledger, rather than requiring large
changes in the perl scripts themselves.

Specifically, the article introduces some techniques that can be used to
output perl structures as XML. From there, we could leverage the FOP
library to produce formatted PDF output. The current implementation of
the FOP libarary is Java-based, but that may not be a permanent
limitation.

There are a number of other benefits to having XML output of
sql-ledger's perl variables, as one can imagine.

Re: Suggestion: Using SAX->XML->FOP for formatted printing

[Don W. <das...@ya...>]

Hi Jeff-

I have been developing my knowledge of XML, XSL,
XALAN, and FOP with respect to documentation.  It is
extremely easy to use perl to output XML, the
formatting to PDF could be done by just having the
perl call the command line version of FOP with an XSL
stylesheet.

Not only would this work for check printing.  It could
result in much prettier and better laid out invoices.

Alternatively, rather than having the perl scripts
output XML, and then make external command line.
Cocoon could be used and Java embedded in the
stylesheet using XSP (special language for embedding
code in Cocoon) to access the database, generate an
XML DOM object.  Then, that object would be formatted
using an XSL stylesheet to create formatted PDF. 
Cocoon can be integrated with Apache, so what would
happen is that PDF creation buttons point to a URL
that Cocoon handles.

If we really want to get pie in the sky, SQL Ledger
could be completely ported to Java, XML and Cocoon...

Regards,
Don




--- Jeff Kowalczyk <jt...@ad...> wrote:
> I came across this article today that would offer
> one possible path for
> SQL ledger to offer the formatted printing features
> that are currently
> being discussed.
> 
>
http://www.xml.com/pub/a/2001/09/19/sax-non-xml-data.html
> 
> I found it interesting because the subject discussed
> would be something
> that could be grafted on top of SQL ledger, rather
> than requiring large
> changes in the perl scripts themselves.
> 
> Specifically, the article introduces some techniques
> that can be used to
> output perl structures as XML. From there, we could
> leverage the FOP
> library to produce formatted PDF output. The current
> implementation of
> the FOP libarary is Java-based, but that may not be
> a permanent
> limitation.
> 
> There are a number of other benefits to having XML
> output of
> sql-ledger's perl variables, as one can imagine.
> 
> 


__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com

RE: Suggestion: Using SAX->XML->FOP for formatted printing

[Jim M. <jim...@wo...>]

Let me preface this with the fact that we like sql-ledger a lot.
Have a look at GNUe and then we should all discuss.
GNUe was missing a backend accounting package, focus has been on the overall
developement environment for XML based forms.
Merging the GNUe frontend with a sql-ledger based backend is probably
easier.
We are currently looking at wrapping some session around sql-ledger for some
related processing of sql-ledger forms. In essence the implementation of a
session surrounding the existing *.pl & *.pm code.

> -----Original Message-----
> From: sql...@li...
> [mailto:sql...@li...]On Behalf Of Don
> Wellington
> Sent: Tuesday, September 25, 2001 4:16 PM
> To: sql...@li...
> Subject: Re: Suggestion: Using SAX->XML->FOP for formatted printing
>
>
> Hi Jeff-
>
> I have been developing my knowledge of XML, XSL,
> XALAN, and FOP with respect to documentation.  It is
> extremely easy to use perl to output XML, the
> formatting to PDF could be done by just having the
> perl call the command line version of FOP with an XSL
> stylesheet.
>
> Not only would this work for check printing.  It could
> result in much prettier and better laid out invoices.
>
> Alternatively, rather than having the perl scripts
> output XML, and then make external command line.
> Cocoon could be used and Java embedded in the
> stylesheet using XSP (special language for embedding
> code in Cocoon) to access the database, generate an
> XML DOM object.  Then, that object would be formatted
> using an XSL stylesheet to create formatted PDF.
> Cocoon can be integrated with Apache, so what would
> happen is that PDF creation buttons point to a URL
> that Cocoon handles.
>
> If we really want to get pie in the sky, SQL Ledger
> could be completely ported to Java, XML and Cocoon...
>
> Regards,
> Don
>
>
>
>
> --- Jeff Kowalczyk <jt...@ad...> wrote:
> > I came across this article today that would offer
> > one possible path for
> > SQL ledger to offer the formatted printing features
> > that are currently
> > being discussed.
> >
> >
> http://www.xml.com/pub/a/2001/09/19/sax-non-xml-data.html
> >
> > I found it interesting because the subject discussed
> > would be something
> > that could be grafted on top of SQL ledger, rather
> > than requiring large
> > changes in the perl scripts themselves.
> >
> > Specifically, the article introduces some techniques
> > that can be used to
> > output perl structures as XML. From there, we could
> > leverage the FOP
> > library to produce formatted PDF output. The current
> > implementation of
> > the FOP libarary is Java-based, but that may not be
> > a permanent
> > limitation.
> >
> > There are a number of other benefits to having XML
> > output of
> > sql-ledger's perl variables, as one can imagine.
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo!
> Messenger. http://im.yahoo.com
>