sql-ledger-users — SQL-Ledger users

Re: [SQL-Ledger-users] LARGE INVENTORY

[Matt B. <ma...@li...>]

Seems like this works for MySQL or Postgres.  With Oracle, you can do
things with ROWNUM to similar effect.

Matt


Matt Benjamin President/CTO

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

tel. 734-761-4689
fax. 734-769-8938
pgr. 734-431-0118

On Wed, 7 Feb 2001 dr...@ss... wrote:


>
> There is a way to pick the next set.  Use the offset keyword.
>
> select * from table where criteria offset START limit LENGTH
>
> --
>   -- Drew Sullivan, <dr...@ss...> -- Toronto, Canada,  +1-416-512-2311
>      Copyleft--all rights reversed
>

Re: [SQL-Ledger-users] LARGE INVENTORY

[<li...@li...>]

It's been rumoured that Roderick A. Anderson said:
> PostgreSQL does have the limit clause which I believe is in the SQL92 and
> SQL99 standards.  It's easy to get into the MySQL (choose your own
> database) has this feature or that thingy but for the most part PostgreSQL
> follows the standands better than the other databases.
> 
>    The problem with the limit statement is it is 'stateless'.  It picks
> the first 'n' records that meet the rest of the selection criteria.  
> There is no easy way to remember the current 'n' items at the database
> level so the the next SELECT statement can pick the next 'n' items.

Not true: use cursors.

DECLARE cursorname CURSOR FOR query;

FETCH count FROM cursorname;

allows you to pick the next n items forward, back, relative, absolute.
etc.

its in postgres.

Note cursors suck for update, because if someone else inserted a record
into the set of N you are looking at with a cursor, things get confusing
as you scroll around.

--linas

Re: [SQL-Ledger-users] LARGE INVENTORY

[<dr...@ss...>]

In message <Pin...@ti...>, "Roderick A.
 Anderson" writes:
> On Tue, 6 Feb 2001, Andrew Sharp wrote:
> 
> >     if($CONFIG{sqllimit} == 1) {
> >         # this presuposes a limit statement in postgresql, but
> >         # I think it has them.  If it doesn't it can be coded
> >         # around anyway.
> 
> PostgreSQL does have the limit clause which I believe is in the SQL92 and
> SQL99 standards.  It's easy to get into the MySQL (choose your own
> database) has this feature or that thingy but for the most part PostgreSQL
> follows the standands better than the other databases.
> 
>    The problem with the limit statement is it is 'stateless'.  It picks
> the first 'n' records that meet the rest of the selection criteria.  
> There is no easy way to remember the current 'n' items at the database
> level so the the next SELECT statement can pick the next 'n' items.

There is a way to pick the next set.  Use the offset keyword.

select * from table where criteria offset START limit LENGTH

-- 
  -- Drew Sullivan, <dr...@ss...> -- Toronto, Canada,  +1-416-512-2311
     Copyleft--all rights reversed

Re: [SQL-Ledger-users] LARGE INVENTORY

[Roderick A. A. <raa...@ti...>]

On Tue, 6 Feb 2001, Andrew Sharp wrote:

>     if($CONFIG{sqllimit} == 1) {
>         # this presuposes a limit statement in postgresql, but
>         # I think it has them.  If it doesn't it can be coded
>         # around anyway.

PostgreSQL does have the limit clause which I believe is in the SQL92 and
SQL99 standards.  It's easy to get into the MySQL (choose your own
database) has this feature or that thingy but for the most part PostgreSQL
follows the standands better than the other databases.

   The problem with the limit statement is it is 'stateless'.  It picks
the first 'n' records that meet the rest of the selection criteria.  
There is no easy way to remember the current 'n' items at the database
level so the the next SELECT statement can pick the next 'n' items.

   The better choice is to select all the records that meet the criteria -
using the DBI - and break them up into groups/bunches to display using a
display limit.

Since I've only been half following the discussion (subscribed to too many
other mailing lists - including two of the PostgreSQL lists) I'm not sure
where the 'convince Dieter' discussion is at currently.  I was mostly
concerned over the repeated question about PostgreSQL having the LIMIT
clause but then realized the LIMIT discussion could be going down the
wrong road.

I hope that we convince Dieter to add some method of limiting the
selection and displayed list so please don't take this as a rebuke.


Good Computing,
Rod
-- 
I really need a signature block!

RE: [SQL-Ledger-users] Documentation?

[Mark T. <ma...@fr...>]

Got it!!

Many thanks to Leo, Thomas, Terry and Dieter.

Appologies for burdening the list with my ignorance :)

> What you have to realize is that Debits and Credits are relative.  When you
> view a bank statement, the bank uses the terms from their perspective:  a

Mark

Mark Tiramani
FREDO Internet Services
ma...@fr...

Re: [SQL-Ledger-users] LARGE INVENTORY

[Andrew S. <an...@me...>]

You mean code sorta like this:



    wilbur_init::header("Entries", $entID);
    print "<img src=3Dentrylist.png alt=3D\"List\"><br><hr>\n";

    $FORM{lim}|=3D 0;=09
    my $qq=3D"select blah,blah,blah=20
                   from entries
                   where blah=3Dblah';
    if($CONFIG{sqllimit} =3D=3D 1) {
        # this presuposes a limit statement in postgresql, but
        # I think it has them.  If it doesn't it can be coded
        # around anyway.
	$qq .=3D "limit $FORM{lim}, $PREF{pListNum}";
    } else {
	my $tlim =3D $FORM{lim} + $PREF{pListNum};
	$qq .=3D "limit $tlim";=20
    }

    my $q =3D $dbh->prepare($qq);
    $q->execute() or print STDERR "$0 $qq\n";

    if($CONFIG{sqllimit} =3D=3D 0) {
	my $tc=3D0;
	while($tc < $FORM{lim}) {
	      my ($blah, $blah) =3D $q->fetchrow_array();
	      $tc++;
	  }
    }

    while(my ($blah, $blah) =3D $q->fetchrow_array()) {
        wilbur::showentry($entID, $blah, $blah);
    }
    $q->finish();

    $qq =3D "select count(entID) from entries where entUID=3D$uID";
    $q =3D $dbh->prepare($qq);
    $q->execute() or print STDERR "$0 $qq\n";
    my ($ct) =3D $q->fetchrow_array();
    $q->finish();   =20

    if(($FORM{lim} - $PREF{pListNum}) >=3D 0 ) { #need prev=20
	my $newlim =3D $FORM{lim} - $PREF{pListNum};
	print "&lt;&lt; <a href=3D\"list.cgi?mode=3Dlist&lim=3D$newlim\">prev</a=
> ]";
    }

    my ($l, $lct) =3D (0, 1);=20
    if($ct > $PREF{pListNum}) {
	print "[";
	do {
	    print "<a href=3D\"list.cgi?mode=3Dlist&lim=3D$l\"> $lct </a>";
	    $l +=3D $PREF{pListNum};
	    $lct++;
	} while($l < $ct);
	print "]\n";
    }
    if(($FORM{lim} + $PREF{pListNum}) < $ct) { # on last already
	my $newlim =3D $FORM{lim} + $PREF{pListNum};
	print "[ <a href=3D\"list.cgi?mode=3Dlist&lim=3D$newlim\">next</a> &gt;&=
gt;\n";
    }


This kind of code is extremely common in programs like this that may have=
 a large number of items to display, and it is desireable to break them u=
p into "pages."  Also, some have mentioned that a user might not want thi=
ngs broken up into pages.  The preference to not have any limit is also t=
here in the above code.

a

Claudio Santana wrote:
>=20
>    I think it would be better to slice this huge page in pages of n
> elements and then display just n elements and give to the user a next
> page link or button so we will just be selecting from the DB all the
> elements but the heavy operation that is generating the page will be
> done with a subset of all the elements. But in this case we should
> keep the state of the module, I mean the "next page" will mean
> different places every time we show it. So we could put that
> information in the "next page" link, we could include the query
> parameters and the next starting ID for the next page, and the same
> for "prev page" . Do I explain my self?
>=20
> Claudio Santana.
>=20
> --- Martin Lillepuu <ma...@li...> escribi=F3: > Thomas Sawyer
> wrote:
> >
> > > I have to get this working with this a large inventory. So I'm
> > looking
> > > at adding some selection criteria limitations to the ic.cgi
> > script. I'm
> > > thinking of adding limiting criteria where one has to select the
> > first
> > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> > How does
> > > this sound to you all? Any other ideas?
> >
> > maybe you should create a new parameter (eq. min_search_str_length)
> > in
> > configuration page, so people with small inventories (like me) can
> > set
> > it to 0 and in your case, it can be set to 2, 3 or whatever. then
> > add
> > code to ic.cgi that displays error message if search string is
> > shorter
> > than value specified in config. does this make any sense or am I
> > over-complicating things again? :)
> >
> > another idea to consider is grouping inventory items, so that you
> > first
> > select group and then only products belonging to specified group
> > are
> > displayed.
> >
> > idea #3 - limit displaying inventory items on one page (does
> > PostgreSQL
> > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > the
> > program + another option to config page?
> >
> > --
> > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> >
>=20
> _________________________________________________________
> Do You Yahoo!?
> Obtenga su direcci=F3n de correo-e gratis @yahoo.com
> en http://correo.espanol.yahoo.com

Re: [SQL-Ledger-users] Documentation?

[Terry C. <tc...@se...>]

On Tue, 6 Feb 2001, Thomas Sawyer wrote:

>  I understand your confusion. I never really have gotten my mind completely
> wrapped around Double Entry Bookkeeping. It seems very, very odd, to
> me. Buy, yes, Asset accounts are debited when they receive value. So
> 
> Don't even consider the meaning of the words Credit and Debit, they are
> quite relative. 

You are right. It pretty much means left(debit) and right(credit)
in relation to the balance sheet.

Our difficulty is that we spend our lives dealing with our personal
bank accounts where a credit means more money in the bank for me.
Credit - good, Debit - bad. We don't realize that it is quite properly
a credit from the bank's point of view - accounts payable to you and
me.

It took me some time, even after I had been using the
double-entry system, for it to "feel" right.



Terry.

Re: [SQL-Ledger-users] Documentation?

[Designer <wir...@ta...>]

Mark Tiramani wrote:

Hello Everyone,

I have found a really good book on databases, and it 
extols PostgreSQL, as a really good database. The book
examines the myth that mysql is faster than PostgreSQL,
due to setup difference, usually be default. This book
covers Postgresql quite extensively, and does cover other
for Lynux systems:

PostgreSQL, MySQL, Mini SQL, Sybase and Oracle

"Database Application Programming with LINUX"

by Brain Jepson, Joan Peckham, Ram Sadasiv

Wiley  ISBN 0-471-35549-6  Copyright 2000


> 
> [snip]
> > keywords mean. The messages are archived at sourceforge. A link to the
> > archive can be found at http://www.sql-ledger.org/misc/support.html
> 
> Thanks, I had checked the archive and read that message, and looked at the screenshots, but I
> fear my problem is even more basic. I feel incredibly stupid, but.....
> 
> I'm using 1.2.7. I understand the general accounting principles but not the terminology involved,
> and no-matter how I link or record a simple incoming invoice I can't get results that make sense
> to me. If someone would be so kind as to give concrete help on the following example I'm sure I
> could get my head around the rest:
> 
> I have a Chequing account used for whole payment, including VAT.
> and an invoice I need to pay for a server that includes 17.5% VAT (UK standard sales tax).
> 
> How should the Chequing account be set-up? I have: 'Asset', 'Account', 'Receivables: Deposit',
> and 'Payables: Payment'  checked.
> 
> What should be entered/selected in the A/P -> 'Add Transaction' form fields for:
> Amount:, VAT:, Paid:
> I tried many daft things but this is the example I would most expect to work:
> 'Amount:'    1175   1820- Office Furniture & Equipment   (gross including VAT)
> 'VAT:'           175   2310-GST
> 'Paid:'         1175   1061-Chequing Account
> 
> However, this results in an Accounts List showing:
> Chequing Account  Credit 1175.00
> Office Furniture & Equipment  Debit  1175.00
> Accounts Payable  Credit  175.00
> GST   Debit  175.00
> 
> Debit total  1350
> Credit total 1350
> 
> Surely that can't be right :)
> 
> BTW I've added one account, 4340, for Sys admin income. All other accounts are using default
> settings.
> 
> Any help appreciated,
> 
> Mark
> 
> Mark Tiramani
> FREDO Internet Services
> ma...@fr...

Re: [SQL-Ledger-users] Documentation?

[Thomas S. <ps...@on...>]

Hi Mark
 I understand your confusion. I never really have gotten my mind completely
wrapped around Double Entry Bookkeeping. It seems very, very odd, to
me. Buy, yes, Asset accounts are debited when they receive value. So
your checking account will be debited to show that it now has money in
it. Further the A/P account that specifies money you owe falls into the
Credit column. Dont ask me why that simply what it says in Accounting,
Barron's Business Review Series, 3rd edition.

Don't even consider the meaning of the words Credit and Debit, they are
quite relative. 

-- 
Thomas Sawyer
ps...@on... - email
(303) 285-3487 x1594 - voicemail/fax



---- "Mark Tiramani" <ma...@fr...> wrote:
> [snip]
> > keywords mean. The messages are archived at sourceforge. A link to
> the
> > archive can be found at http://www.sql-ledger.org/misc/support.html
> 
> Thanks, I had checked the archive and read that message, and looked
> at the screenshots, but I 
> fear my problem is even more basic. I feel incredibly stupid, but.....
> 
> I'm using 1.2.7. I understand the general accounting principles but
> not the terminology involved, 
> and no-matter how I link or record a simple incoming invoice I can't
> get results that make sense 
> to me. If someone would be so kind as to give concrete help on the
> following example I'm sure I 
> could get my head around the rest:
> 
> I have a Chequing account used for whole payment, including VAT.
> and an invoice I need to pay for a server that includes 17.5% VAT (UK
> standard sales tax).
> 
> How should the Chequing account be set-up? I have: 'Asset', 'Account',
> 'Receivables: Deposit', 
> and 'Payables: Payment'  checked.
> 
> What should be entered/selected in the A/P -> 'Add Transaction' form
> fields for:
> Amount:, VAT:, Paid:
> I tried many daft things but this is the example I would most expect
> to work:
> 'Amount:'    1175   1820- Office Furniture & Equipment   (gross including
> VAT)
> 'VAT:'           175   2310-GST
> 'Paid:'         1175   1061-Chequing Account
> 
> However, this results in an Accounts List showing:
> Chequing Account  Credit 1175.00
> Office Furniture & Equipment  Debit  1175.00
> Accounts Payable  Credit  175.00
> GST   Debit  175.00
> 
> Debit total  1350
> Credit total 1350
> 
> Surely that can't be right :)
> 
> BTW I've added one account, 4340, for Sys admin income. All other accounts
> are using default 
> settings.
> 
> Any help appreciated,
> 
> Mark
> 
> Mark Tiramani
> FREDO Internet Services
> ma...@fr...
> 
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

Re: [SQL-Ledger-users] Documentation?

[Mark T. <ma...@fr...>]

> A checking account is an asset account.


I did have it marked as an 'Asset' account.

(Is this a Checking Account or a Chequing Account??)


<color><param>0000,0000,0000</param>> If you use the account to pay bills =
and deposit money received then check

> the box in the column Receivables -> Deposit and Payables ->

> Payment. This will include the account in the drop down lists


</color>As I illustrated previously this is exactly the way it was set up.=
 


<color><param>0000,0000,0000</param>> In your sample transaction you had n=
ot fully paid for the furniture

> thus leaving you with 175 outstanding in payables.


</color>So in /sql-ledger/ap.cgi?action=3Dadd 'Amount:' on row 6 means 'Ne=
t Amount:' ?

In the same form doesn't 'Paid:' mean 'Paid From:' ?


Again: the 'computer' was bought by my company for =A31,175 gross and I pa=
id =A31,175, from 
'Chequing' (Checking?). Please see my previous email below.


If I start with =A30 in Checking how can I still get =A31,175 credited to =
the 'Chequing Account' to give 
a total 'Credit' of =A31,175.00. ..... Surely I should have a 'Debit' of =A3=
1,175 in 'Checking', whichever 
way the VAT is accounted for ??


I'm a programmer not a mathematician, but is my math really that bad!? :)

I obviously don't understand what a 'Checking Account' really is. To me it=
 represents my Bank 
balance and available funds.


Mark


<color><param>0000,0000,0000</param>> > How should the Chequing account be=
 set-up? I have: 'Asset', 'Account', 'Receivables: Deposit', and

> > 'Payables: Payment'  checked.

> > 

> > What should be entered/selected in the A/P -> 'Add Transaction' form f=
ields for:

> > Amount:, VAT:, Paid:

> > I tried many daft things but this is the example I would most expect t=
o work:

> > 'Amount:'    1175   1820- Office Furniture & Equipment   (gross includ=
ing VAT)

> > 'VAT:'           175   2310-GST

> > 'Paid:'         1175   1061-Chequing Account

> > 

> > However, this results in an Accounts List showing:

> > Chequing Account  Credit 1175.00

> > Office Furniture & Equipment  Debit  1175.00

> > Accounts Payable  Credit  175.00

> > GST   Debit  175.00

> > 

> > Debit total  1350

> > Credit total 1350

> > 

> > Surely that can't be right :)


Mark Tiramani
FREDO Internet Services
ma...@fr...

Re: [SQL-Ledger-users] LARGE INVENTORY

[Thomas S. <ps...@on...>]

Well for starters we simply need to create a start record count variable
and an end record count variable: $form->{startcnt} and $form->{endcnt}.
For now fix them to 0 and 1000, respectivly.

Then in the search_for_item function in the ic.cgi script replace:

$query = qq|SELECT id, number, description, onhand, unit, sellprice
                   FROM parts WHERE $where
                   ORDER BY $from->{sort}
           |;

with:

$query = qq|SELECT id, number, description, onhand, unit, sellprice
                   FROM parts WHERE $where
                   ORDER BY $from->{sort}
                   LIMIT $form->{endcnt}, $form-{startcnt}
           |;

This should work fine and open it up for adding pages down the line.

-- 
Thomas Sawyer
ps...@on... - email
(303) 285-3487 x1594 - voicemail/fax



---- Matt Benjamin <ma...@li...> wrote:
> 
> The feature is easy enough to code, and I'd be willing to, but it sounds
> like Dieter needs a little more convincing of its utility :)
> 
> 
> Matt
> 
> 
> >
> > So who wants to do it?
> >
> 
> 
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

Re: [SQL-Ledger-users] LARGE INVENTORY

[Thomas S. <ps...@on...>]

I think Dieter might have meant "in implementation". Paging would certainly
be a acceptable and sometimes useful feature, but it may not be so easy
to code. I'd rather see an effective compromise for now and get the new
version out rather then wait for the inventory search code to be completly
re-written.

-- 
Thomas Sawyer
ps...@on... - email
(303) 285-3487 x1594 - voicemail/fax



---- Matt Benjamin <ma...@li...> wrote:
> 
> Why not, exactly?  It seems like a sensible approach when you really
> do
> want to browse many pages of data.  That must be why even the most
> recent
> search engines provide this feature.
> 
> I certainly wouldn't substitute paging for search criteria, but again,
> sometimes you want to browse.
> 
> Matt
> 
> > Slicing output into pages does not work very well.
> >
> 
> 
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

Re: [SQL-Ledger-users] LARGE INVENTORY

[Matt B. <ma...@li...>]

The feature is easy enough to code, and I'd be willing to, but it sounds
like Dieter needs a little more convincing of its utility :)


Matt


>
> So who wants to do it?
>

Re: [SQL-Ledger-users] LARGE INVENTORY

[Thomas S. <ps...@on...>]

Dieter,

I don't see how adding a character limit will help both sides in this.
How would you implement this? If you add a character limit then how does
someone pull up a full listing?

Honestly, I think the paging idea was right-on. And that should be the
direction to move in. I didn't realize it at first, but it would not
be that hard.

Here, follow this link and see http://www.oreillynet.com/lpt/a/448.

It is as simple as putting a LIMIT clause in the sql statement. Whether
its a fixed or variable limit is a matter of whether you want to put
a field on the search page for it or not. (Where 0 or blank could mean
all.) 

Yet I would like to point out that the poeple who say they don't want
a limit so they can pull up all their inventory are exactly the ones
who do not have a large inventory to pull up! That's why I think simply
putting a fixed limit of 1,000 for now would be a good compromise, without
much fuss.

-- 
Thomas Sawyer
ps...@on... - email

---- Dieter Simader <dsi...@sq...> wrote:
> Slicing output into pages does not work very well.
> 
> I'll add an option to limit searches by forcing users to enter a minimum
> number of characters for those who can't teach their users to enter
> something. This leaves the program the way it is for people who like
> to
> produce a complete inventory listing and limits output for those who
> need
> a limit.
> 
> It used to be in version 0.1, I'll add it again for version 1.4
> 
> 
> 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, 6 Feb 2001, Matt Benjamin wrote:
> 
> > 
> > I like this suggestion.  It would allow you to browse all available
> data
> > in user-configurable increments.
> > 
> > It is also a very familiar interface on the web, which would make
> it easy
> > and comfortable for end-users to learn.  (Reading "Phillip and Alex's
> > Guide to Web Publishing" has opened my eyes to the importance of
> > easy-to-learn interfaces, I think.)
> > 
> > Matt
> > 
> > 
> > Matt Benjamin President/CTO
> > 
> > The Linux Box
> > 206 South Fifth Ave. Suite 150
> > Ann Arbor, MI  48104
> > 
> > tel. 734-761-4689
> > fax. 734-769-8938
> > pgr. 734-431-0118
> > 
> > On Tue, 6 Feb 2001, [iso-8859-1] Claudio Santana wrote:
> > 
> > >    I think it would be better to slice this huge page in pages
> of n
> > > elements and then display just n elements and give to the user
> a next
> > > page link or button so we will just be selecting from the DB all
> the
> > > elements but the heavy operation that is generating the page will
> be
> > > done with a subset of all the elements. But in this case we should
> > > keep the state of the module, I mean the "next page" will mean
> > > different places every time we show it. So we could put that
> > > information in the "next page" link, we could include the query
> > > parameters and the next starting ID for the next page, and the
> same
> > > for "prev page" . Do I explain my self?
> > >
> > > Claudio Santana.
> > >
> > > --- Martin Lillepuu <ma...@li...> escribió: > Thomas Sawyer
> > > wrote:
> > > >
> > > > > I have to get this working with this a large inventory. So
> I'm
> > > > looking
> > > > > at adding some selection criteria limitations to the ic.cgi
> > > > script. I'm
> > > > > thinking of adding limiting criteria where one has to select
> the
> > > > first
> > > > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy,
> Zz)
> > > > How does
> > > > > this sound to you all? Any other ideas?
> > > >
> > > > maybe you should create a new parameter (eq. min_search_str_length)
> > > > in
> > > > configuration page, so people with small inventories (like me)
> can
> > > > set
> > > > it to 0 and in your case, it can be set to 2, 3 or whatever.
> then
> > > > add
> > > > code to ic.cgi that displays error message if search string is
> > > > shorter
> > > > than value specified in config. does this make any sense or am
> I
> > > > over-complicating things again? :)
> > > >
> > > > another idea to consider is grouping inventory items, so that
> you
> > > > first
> > > > select group and then only products belonging to specified group
> > > > are
> > > > displayed.
> > > >
> > > > idea #3 - limit displaying inventory items on one page (does
> > > > PostgreSQL
> > > > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > > > the
> > > > program + another option to config page?
> > > >
> > > > --
> > > > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> > > >
> > >
> > >
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Obtenga su dirección de correo-e gratis @yahoo.com
> > > en http://correo.espanol.yahoo.com
> > >
> > 
> > 
> > 
> 
> 
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

Re: [SQL-Ledger-users] LARGE INVENTORY

[Matt B. <ma...@li...>]

Why not, exactly?  It seems like a sensible approach when you really do
want to browse many pages of data.  That must be why even the most recent
search engines provide this feature.

I certainly wouldn't substitute paging for search criteria, but again,
sometimes you want to browse.

Matt

> Slicing output into pages does not work very well.
>

Re: [SQL-Ledger-users] LARGE INVENTORY

[Thomas S. <ps...@on...>]

I see! You mean to offer both -- a user definable # or records returned,
but per page, and then links to the other pages (ie. back, next, 1-50,
51-100, etc.) Perfect!

So who wants to do it?

Also, Dieter Simader, where does version 1.4 stand? Is it close to realease?
How will our changes be effective with that new version? Do we just tell
you about them and you'll see about putting them in? Guess I'm a little
confused about the how's of this collabrotive open-source development
thing. I looked on ScourceForge and all I saw was the 1.2.5 release,
not even the current 1.2.7. Right now I'm becoming a SourceForge member.
I'm thinking, this might make a difference and I'd be able to find the
lastest in-development version (1.4). Is CVS being used here?


Thomas Sawyer
ps...@on... - email

---- Matt Benjamin <ma...@li...> wrote:
> 
> I like this suggestion.  It would allow you to browse all available
> data
> in user-configurable increments.
> 
> It is also a very familiar interface on the web, which would make it
> easy
> and comfortable for end-users to learn.  (Reading "Phillip and Alex's
> Guide to Web Publishing" has opened my eyes to the importance of
> easy-to-learn interfaces, I think.)
> 
> Matt
> 
> 
> Matt Benjamin President/CTO
> 
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
> 
> tel. 734-761-4689
> fax. 734-769-8938
> pgr. 734-431-0118
> 
> On Tue, 6 Feb 2001, [iso-8859-1] Claudio Santana wrote:
> 
> >    I think it would be better to slice this huge page in pages of
> n
> > elements and then display just n elements and give to the user a
> next
> > page link or button so we will just be selecting from the DB all
> the
> > elements but the heavy operation that is generating the page will
> be
> > done with a subset of all the elements. But in this case we should
> > keep the state of the module, I mean the "next page" will mean
> > different places every time we show it. So we could put that
> > information in the "next page" link, we could include the query
> > parameters and the next starting ID for the next page, and the same
> > for "prev page" . Do I explain my self?
> >
> > Claudio Santana.
> >
> > --- Martin Lillepuu <ma...@li...> escribió: > Thomas Sawyer
> > wrote:
> > >
> > > > I have to get this working with this a large inventory. So I'm
> > > looking
> > > > at adding some selection criteria limitations to the ic.cgi
> > > script. I'm
> > > > thinking of adding limiting criteria where one has to select
> the
> > > first
> > > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> > > How does
> > > > this sound to you all? Any other ideas?
> > >
> > > maybe you should create a new parameter (eq. min_search_str_length)
> > > in
> > > configuration page, so people with small inventories (like me)
> can
> > > set
> > > it to 0 and in your case, it can be set to 2, 3 or whatever. then
> > > add
> > > code to ic.cgi that displays error message if search string is
> > > shorter
> > > than value specified in config. does this make any sense or am
> I
> > > over-complicating things again? :)
> > >
> > > another idea to consider is grouping inventory items, so that you
> > > first
> > > select group and then only products belonging to specified group
> > > are
> > > displayed.
> > >
> > > idea #3 - limit displaying inventory items on one page (does
> > > PostgreSQL
> > > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > > the
> > > program + another option to config page?
> > >
> > > --
> > > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> > >
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Obtenga su dirección de correo-e gratis @yahoo.com
> > en http://correo.espanol.yahoo.com
> >
> 
> 
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

Re: [SQL-Ledger-users] LARGE INVENTORY

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

Slicing output into pages does not work very well.

I'll add an option to limit searches by forcing users to enter a minimum
number of characters for those who can't teach their users to enter
something. This leaves the program the way it is for people who like to
produce a complete inventory listing and limits output for those who need
a limit.

It used to be in version 0.1, I'll add it again for version 1.4


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

On Tue, 6 Feb 2001, Matt Benjamin wrote:

>=20
> I like this suggestion.  It would allow you to browse all available dat=
a
> in user-configurable increments.
>=20
> It is also a very familiar interface on the web, which would make it ea=
sy
> and comfortable for end-users to learn.  (Reading "Phillip and Alex's
> Guide to Web Publishing" has opened my eyes to the importance of
> easy-to-learn interfaces, I think.)
>=20
> Matt
>=20
>=20
> Matt Benjamin President/CTO
>=20
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
>=20
> tel. 734-761-4689
> fax. 734-769-8938
> pgr. 734-431-0118
>=20
> On Tue, 6 Feb 2001, [iso-8859-1] Claudio Santana wrote:
>=20
> >    I think it would be better to slice this huge page in pages of n
> > elements and then display just n elements and give to the user a next
> > page link or button so we will just be selecting from the DB all the
> > elements but the heavy operation that is generating the page will be
> > done with a subset of all the elements. But in this case we should
> > keep the state of the module, I mean the "next page" will mean
> > different places every time we show it. So we could put that
> > information in the "next page" link, we could include the query
> > parameters and the next starting ID for the next page, and the same
> > for "prev page" . Do I explain my self?
> >
> > Claudio Santana.
> >
> > --- Martin Lillepuu <ma...@li...> escribi=F3: > Thomas Sawyer
> > wrote:
> > >
> > > > I have to get this working with this a large inventory. So I'm
> > > looking
> > > > at adding some selection criteria limitations to the ic.cgi
> > > script. I'm
> > > > thinking of adding limiting criteria where one has to select the
> > > first
> > > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> > > How does
> > > > this sound to you all? Any other ideas?
> > >
> > > maybe you should create a new parameter (eq. min_search_str_length)
> > > in
> > > configuration page, so people with small inventories (like me) can
> > > set
> > > it to 0 and in your case, it can be set to 2, 3 or whatever. then
> > > add
> > > code to ic.cgi that displays error message if search string is
> > > shorter
> > > than value specified in config. does this make any sense or am I
> > > over-complicating things again? :)
> > >
> > > another idea to consider is grouping inventory items, so that you
> > > first
> > > select group and then only products belonging to specified group
> > > are
> > > displayed.
> > >
> > > idea #3 - limit displaying inventory items on one page (does
> > > PostgreSQL
> > > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > > the
> > > program + another option to config page?
> > >
> > > --
> > > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> > >
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Obtenga su direcci=F3n de correo-e gratis @yahoo.com
> > en http://correo.espanol.yahoo.com
> >
>=20
>=20
>=20

Re: [SQL-Ledger-users] Documentation?

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

A checking account is an asset account.

If you use the account to pay bills and deposit money received then check
the box in the column Receivables -> Deposit and Payables ->
Payment. This will include the account in the drop down lists

In your sample transaction you had not fully paid for the furniture
thus leaving you with 175 outstanding in payables.


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, 6 Feb 2001, Mark Tiramani wrote:

> [snip]
> > keywords mean. The messages are archived at sourceforge. A link to the
> > archive can be found at http://www.sql-ledger.org/misc/support.html
> 
> Thanks, I had checked the archive and read that message, and looked at the screenshots, but I 
> fear my problem is even more basic. I feel incredibly stupid, but.....
> 
> I'm using 1.2.7. I understand the general accounting principles but not the terminology involved, 
> and no-matter how I link or record a simple incoming invoice I can't get results that make sense 
> to me. If someone would be so kind as to give concrete help on the following example I'm sure I 
> could get my head around the rest:
> 
> I have a Chequing account used for whole payment, including VAT.
> and an invoice I need to pay for a server that includes 17.5% VAT (UK standard sales tax).
> 
> How should the Chequing account be set-up? I have: 'Asset', 'Account', 'Receivables: Deposit', 
> and 'Payables: Payment'  checked.
> 
> What should be entered/selected in the A/P -> 'Add Transaction' form fields for:
> Amount:, VAT:, Paid:
> I tried many daft things but this is the example I would most expect to work:
> 'Amount:'    1175   1820- Office Furniture & Equipment   (gross including VAT)
> 'VAT:'           175   2310-GST
> 'Paid:'         1175   1061-Chequing Account
> 
> However, this results in an Accounts List showing:
> Chequing Account  Credit 1175.00
> Office Furniture & Equipment  Debit  1175.00
> Accounts Payable  Credit  175.00
> GST   Debit  175.00
> 
> Debit total  1350
> Credit total 1350
> 
> Surely that can't be right :)
> 
> BTW I've added one account, 4340, for Sys admin income. All other accounts are using default 
> settings.
> 
> Any help appreciated,
> 
> Mark
> 
> Mark Tiramani
> FREDO Internet Services
> ma...@fr...
> 
> 

Re: [SQL-Ledger-users] LARGE INVENTORY

[Matt B. <ma...@li...>]

I like this suggestion.  It would allow you to browse all available data
in user-configurable increments.

It is also a very familiar interface on the web, which would make it easy
and comfortable for end-users to learn.  (Reading "Phillip and Alex's
Guide to Web Publishing" has opened my eyes to the importance of
easy-to-learn interfaces, I think.)

Matt


Matt Benjamin President/CTO

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

tel. 734-761-4689
fax. 734-769-8938
pgr. 734-431-0118

On Tue, 6 Feb 2001, [iso-8859-1] Claudio Santana wrote:

>    I think it would be better to slice this huge page in pages of n
> elements and then display just n elements and give to the user a next
> page link or button so we will just be selecting from the DB all the
> elements but the heavy operation that is generating the page will be
> done with a subset of all the elements. But in this case we should
> keep the state of the module, I mean the "next page" will mean
> different places every time we show it. So we could put that
> information in the "next page" link, we could include the query
> parameters and the next starting ID for the next page, and the same
> for "prev page" . Do I explain my self?
>
> Claudio Santana.
>
> --- Martin Lillepuu <ma...@li...> escribi=F3: > Thomas Sawyer
> wrote:
> >
> > > I have to get this working with this a large inventory. So I'm
> > looking
> > > at adding some selection criteria limitations to the ic.cgi
> > script. I'm
> > > thinking of adding limiting criteria where one has to select the
> > first
> > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> > How does
> > > this sound to you all? Any other ideas?
> >
> > maybe you should create a new parameter (eq. min_search_str_length)
> > in
> > configuration page, so people with small inventories (like me) can
> > set
> > it to 0 and in your case, it can be set to 2, 3 or whatever. then
> > add
> > code to ic.cgi that displays error message if search string is
> > shorter
> > than value specified in config. does this make any sense or am I
> > over-complicating things again? :)
> >
> > another idea to consider is grouping inventory items, so that you
> > first
> > select group and then only products belonging to specified group
> > are
> > displayed.
> >
> > idea #3 - limit displaying inventory items on one page (does
> > PostgreSQL
> > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > the
> > program + another option to config page?
> >
> > --
> > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> >
>
>
> _________________________________________________________
> Do You Yahoo!?
> Obtenga su direcci=F3n de correo-e gratis @yahoo.com
> en http://correo.espanol.yahoo.com
>

Re: [SQL-Ledger-users] LARGE INVENTORY

[Matt B. <ma...@li...>]

Being able to scroll through long listings, possibly with a configurable
page size, seems like an (eventual) requirement.  I do not see the value
in getting just the top 1000 (or however many) entries.


Matt


Matt Benjamin President/CTO

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

tel. 734-761-4689
fax. 734-769-8938
pgr. 734-431-0118

On Tue, 6 Feb 2001, Thomas Sawyer wrote:

> I thought about that. In fact I was looking at Border's book search site
> and they have a neat way of doing this by having links for each set at
> the top of the page i.e. 1-50 | 51-100 | 101-150 ...etc. But its not
> such a great idea I think b/c if you do a serach and your item ends up
> on the 2nd or 3rd or 4th... page then you have to go through multiple
> links (and hence waitings) to find it. Its much easier to scroll down
> to find something and sql-ledger can load a 1,000 items pretty fast.
>
> --
> Thomas Sawyer
> ps...@on... - email
> (303) 285-3487 x1594 - voicemail/fax
>
>
>
> ---- =3D?iso-8859-1?q?Claudio=3D20Santana?=3D <tra...@ya...> wrote=
:
> >    I think it would be better to slice this huge page in pages of n
> > elements and then display just n elements and give to the user a next
> > page link or button so we will just be selecting from the DB all the
> > elements but the heavy operation that is generating the page will be
> > done with a subset of all the elements. But in this case we should
> > keep the state of the module, I mean the "next page" will mean
> > different places every time we show it. So we could put that
> > information in the "next page" link, we could include the query
> > parameters and the next starting ID for the next page, and the same
> > for "prev page" . Do I explain my self?
> >
> > Claudio Santana.
> >
> > --- Martin Lillepuu <ma...@li...> escribi=F3: > Thomas Sawyer
> > wrote:
> > >
> > > > I have to get this working with this a large inventory. So I'm
> > > looking
> > > > at adding some selection criteria limitations to the ic.cgi
> > > script. I'm
> > > > thinking of adding limiting criteria where one has to select the
> > > first
> > > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> > > How does
> > > > this sound to you all? Any other ideas?
> > >
> > > maybe you should create a new parameter (eq. min_search_str_length)
> > > in
> > > configuration page, so people with small inventories (like me) can
> > > set
> > > it to 0 and in your case, it can be set to 2, 3 or whatever. then
> > > add
> > > code to ic.cgi that displays error message if search string is
> > > shorter
> > > than value specified in config. does this make any sense or am I
> > > over-complicating things again? :)
> > >
> > > another idea to consider is grouping inventory items, so that you
> > > first
> > > select group and then only products belonging to specified group
> > > are
> > > displayed.
> > >
> > > idea #3 - limit displaying inventory items on one page (does
> > > PostgreSQL
> > > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > > the
> > > program + another option to config page?
> > >
> > > --
> > > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> > >
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Obtenga su direcci=F3n de correo-e gratis @yahoo.com
> > en http://correo.espanol.yahoo.com
> >
> >
>
> __________________________________________________
> FREE voicemail, email, and fax...all in one place.
> Sign Up Now! http://www.onebox.com
>
>

Re: [SQL-Ledger-users] LARGE INVENTORY

[Thomas S. <ps...@on...>]

I thought about that. In fact I was looking at Border's book search site
and they have a neat way of doing this by having links for each set at
the top of the page i.e. 1-50 | 51-100 | 101-150 ...etc. But its not
such a great idea I think b/c if you do a serach and your item ends up
on the 2nd or 3rd or 4th... page then you have to go through multiple
links (and hence waitings) to find it. Its much easier to scroll down
to find something and sql-ledger can load a 1,000 items pretty fast.

-- 
Thomas Sawyer
ps...@on... - email
(303) 285-3487 x1594 - voicemail/fax



---- =?iso-8859-1?q?Claudio=20Santana?= <tra...@ya...> wrote:
>    I think it would be better to slice this huge page in pages of n
> elements and then display just n elements and give to the user a next
> page link or button so we will just be selecting from the DB all the
> elements but the heavy operation that is generating the page will be
> done with a subset of all the elements. But in this case we should
> keep the state of the module, I mean the "next page" will mean
> different places every time we show it. So we could put that
> information in the "next page" link, we could include the query
> parameters and the next starting ID for the next page, and the same
> for "prev page" . Do I explain my self?
> 
> Claudio Santana.
> 
> --- Martin Lillepuu <ma...@li...> escribió: > Thomas Sawyer
> wrote:
> > 
> > > I have to get this working with this a large inventory. So I'm
> > looking
> > > at adding some selection criteria limitations to the ic.cgi
> > script. I'm
> > > thinking of adding limiting criteria where one has to select the
> > first
> > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> > How does
> > > this sound to you all? Any other ideas?
> > 
> > maybe you should create a new parameter (eq. min_search_str_length)
> > in
> > configuration page, so people with small inventories (like me) can
> > set
> > it to 0 and in your case, it can be set to 2, 3 or whatever. then
> > add
> > code to ic.cgi that displays error message if search string is
> > shorter
> > than value specified in config. does this make any sense or am I
> > over-complicating things again? :)
> > 
> > another idea to consider is grouping inventory items, so that you
> > first
> > select group and then only products belonging to specified group
> > are
> > displayed.
> > 
> > idea #3 - limit displaying inventory items on one page (does
> > PostgreSQL
> > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > the
> > program + another option to config page?
> > 
> > --
> > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> > 
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Obtenga su dirección de correo-e gratis @yahoo.com
> en http://correo.espanol.yahoo.com
> 
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

Re: [SQL-Ledger-users] LARGE INVENTORY

[<tra...@ya...>]

   I think it would be better to slice this huge page in pages of n
elements and then display just n elements and give to the user a next
page link or button so we will just be selecting from the DB all the
elements but the heavy operation that is generating the page will be
done with a subset of all the elements. But in this case we should
keep the state of the module, I mean the "next page" will mean
different places every time we show it. So we could put that
information in the "next page" link, we could include the query
parameters and the next starting ID for the next page, and the same
for "prev page" . Do I explain my self?

Claudio Santana.

--- Martin Lillepuu <ma...@li...> escribió: > Thomas Sawyer
wrote:
> 
> > I have to get this working with this a large inventory. So I'm
> looking
> > at adding some selection criteria limitations to the ic.cgi
> script. I'm
> > thinking of adding limiting criteria where one has to select the
> first
> > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> How does
> > this sound to you all? Any other ideas?
> 
> maybe you should create a new parameter (eq. min_search_str_length)
> in
> configuration page, so people with small inventories (like me) can
> set
> it to 0 and in your case, it can be set to 2, 3 or whatever. then
> add
> code to ic.cgi that displays error message if search string is
> shorter
> than value specified in config. does this make any sense or am I
> over-complicating things again? :)
> 
> another idea to consider is grouping inventory items, so that you
> first
> select group and then only products belonging to specified group
> are
> displayed.
> 
> idea #3 - limit displaying inventory items on one page (does
> PostgreSQL
> have equivalent to MySQL LIMIT?). Maybe implement this throughout
> the
> program + another option to config page?
> 
> --
> Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> 


_________________________________________________________
Do You Yahoo!?
Obtenga su dirección de correo-e gratis @yahoo.com
en http://correo.espanol.yahoo.com

[SQL-Ledger-users] More Examination of database tables

[Thomas S. <ps...@on...>]

Some difficulties:

What is the 'allocated' field used for in the invoice table? Where is
it used --in what scripts?

Also how can I tell by looking at an invoice record which header record
goes to it --the trans_id matches the id of the 'ar' or 'ap' record,
but how can you determine which of the two table it relates too?

-- 
Thomas Sawyer
ps...@on... - email
(303) 285-3487 x1594 - voicemail/fax



---- "Thomas Sawyer" <ps...@on...> wrote:
> Well I'm doing indepth analysis here trying to understand everything
> and its starting to unfold for me.
> 
> I see now how the 'ar' and 'ap' tables serve as header records for
> customer
> invoices and vendor invoices, respectively. And that for both the detail
> line item records go into the 'invoice' table.
> 
> I am unclear what the 'ordnumber' field is for in the 'ap' table, but
> I assume that it is for the idetification of the Vendor's Invoice,
> i.e
> the number the vendor put on it. After making this conclusion, it would
> seem appropriate that there be a 'ordnumber' field in the 'ar' table
> too, to be used for customer purchase order numbers if they have one.
> 
> Am I on the right track here? I hope so b/c I took the inititive and
> created near-exact copies of the 'ar', 'ap' and 'invoice' tables to
> use
> for customer orders and purchase orders. I figure they will work nearly
> the same. So now I have an 'so' table for sales orders and a 'po' table
> for purchase orders and an 'order' table for their line items.
> 
> Now I'm going to copy the ir.cgi and is.cgi scripts and change them
> to
> match, making sure to remove any code that creates actual transactions.
> 
> So in proceeding is there anything I need to watch for?
> 
> 
> 
> 
> __________________________________________________
> FREE voicemail, email, and fax...all in one place.
> Sign Up Now! http://www.onebox.com
> 
> 
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

[SQL-Ledger-users] Examination of database tables

[Thomas S. <ps...@on...>]

Well I'm doing indepth analysis here trying to understand everything
and its starting to unfold for me.

I see now how the 'ar' and 'ap' tables serve as header records for customer
invoices and vendor invoices, respectively. And that for both the detail
line item records go into the 'invoice' table.

I am unclear what the 'ordnumber' field is for in the 'ap' table, but
I assume that it is for the idetification of the Vendor's Invoice, i.e
the number the vendor put on it. After making this conclusion, it would
seem appropriate that there be a 'ordnumber' field in the 'ar' table
too, to be used for customer purchase order numbers if they have one.

Am I on the right track here? I hope so b/c I took the inititive and
created near-exact copies of the 'ar', 'ap' and 'invoice' tables to use
for customer orders and purchase orders. I figure they will work nearly
the same. So now I have an 'so' table for sales orders and a 'po' table
for purchase orders and an 'order' table for their line items.

Now I'm going to copy the ir.cgi and is.cgi scripts and change them to
match, making sure to remove any code that creates actual transactions.

So in proceeding is there anything I need to watch for?




__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com

Re: [SQL-Ledger-users] Documentation?

[Mark T. <ma...@fr...>]

[snip]
> keywords mean. The messages are archived at sourceforge. A link to the
> archive can be found at http://www.sql-ledger.org/misc/support.html

Thanks, I had checked the archive and read that message, and looked at the screenshots, but I 
fear my problem is even more basic. I feel incredibly stupid, but.....

I'm using 1.2.7. I understand the general accounting principles but not the terminology involved, 
and no-matter how I link or record a simple incoming invoice I can't get results that make sense 
to me. If someone would be so kind as to give concrete help on the following example I'm sure I 
could get my head around the rest:

I have a Chequing account used for whole payment, including VAT.
and an invoice I need to pay for a server that includes 17.5% VAT (UK standard sales tax).

How should the Chequing account be set-up? I have: 'Asset', 'Account', 'Receivables: Deposit', 
and 'Payables: Payment'  checked.

What should be entered/selected in the A/P -> 'Add Transaction' form fields for:
Amount:, VAT:, Paid:
I tried many daft things but this is the example I would most expect to work:
'Amount:'    1175   1820- Office Furniture & Equipment   (gross including VAT)
'VAT:'           175   2310-GST
'Paid:'         1175   1061-Chequing Account

However, this results in an Accounts List showing:
Chequing Account  Credit 1175.00
Office Furniture & Equipment  Debit  1175.00
Accounts Payable  Credit  175.00
GST   Debit  175.00

Debit total  1350
Credit total 1350

Surely that can't be right :)

BTW I've added one account, 4340, for Sys admin income. All other accounts are using default 
settings.

Any help appreciated,

Mark

Mark Tiramani
FREDO Internet Services
ma...@fr...