sql-ledger-users — SQL-Ledger users

closing transactions -- preventing modifications

[Benjamin L. <ben...@co...>]

This is only tested with v1.4.4. Although it will work with the
previous 1.4 versions with a little change to the setup process.

Some people might like this little feature.

It's a close function, such that transactions previous to a set date
can no longer be inserted or updated or deleted.

This allows closing of records, especially in respect to finishing off
the financial year. You don't want to back date anything or delete
your data.

It's implemented in a bit of PL/pgSQL and Perl for the frontend so you
should have fun installing it. ;-P

Be VERY careful with this feature as it only allows updating of the
closing date going FORWARDS in time. Should you accidently close off
to a particular date (especially in the future) you'll have to drop
the trigger manually and update the 'close' table. I'll leave this
part as a learning exercise. ;-)

Actually the only reason the PL/SQL works so well with such a small
amount of code is because the SL code uses 'commit' in appropriate
places. ;-) Yay.


Edit line 26 close.sql with the 'youruser' that you use to connect to
your accounting database.

Run psql

import the sql with:

\i close.sql

Put close.pl into bin/mozilla/ (I haven't written anything for the
other interfaces yet). Symlink close.pl -> am.pl, like all (most of)
the other scripts.

Put the following into the left menu side in menu.pl (I've attached my
menu.pl as well).

<!-- snip -->

<p><b>|.$locale->text('Close').qq|</b>

<li><a href=close.pl?path=$form->{path}&action=close&title=Close%20Date&login=$form->{login} target=main_window>|.$locale->text('Close Date').qq|</a>

<!-- snip -->



I think that's it.

Have fun,
Ben.

-- 
B.      http://makelinux.org/    "Always real."    http://realthought.net/
__________________________________________________________________________
Brontosaurus Principle:
	Organizations can grow faster than their brains can manage them
	in relation to their environment and to their own physiology:  when
	this occurs, they are an endangered species.
		-- Thomas K. Connellan

Re: Compilation errors

[Jess <je...@oz...>]

 I am getting the same error but under Apache in Windows 2000 Pro.
I think some file must have a corrupt bit or something I have asked for =
certain files from a working system to see if the problem gets solved.

Regards Jess
  ----- Original Message -----=20
  From: nyk=20
  To: sql...@li...=20
  Sent: Wednesday, 30 May, 2001 4:44 PM
  Subject: Compilation errors


      I downloaded your SQL-Ledger 1.4.3 and trying to install onto my =
RedHat linux box running RedHat 6.2. There were no problems in getting =
the users created but when I wanted to login into the system, following =
message appears in my server error log:

  Unknown error
  Compilation failed in require at =
/home/paging2.easycall.com.my/htdocs/sql-ledger/login.pl line 61.
  [Mon May 28 22:22:59 2001] [error] [client 172.1.1.20] Premature end =
of script headers: =
/home/paging2.easycall.com.my/htdocs/sql-ledger/login.pl

      Is there anything else that I have missed out in configuring the =
system? To my knowledge, I have correctly installed the DBD::Pg drivers =
as well as the DBI

      I appreciate if any help can be rendered.


  Regards

  Ng Yit Khuang
  ny...@ru...

Re: [SQL-Ledger-users] Spanish version

[Maria G. F. <mg...@ma...>]

I agree with Antonio and German, one version in spanish is enough for me,
even though I can see Dieter's point when he thought of country versions =
for
the language modules.

For example, I am no accountant, but a consultant, so technology and
changing terms come easily to me...
Accountants tend to be very picky about their terminology and how you cal=
l
this and that, and even though I know that they do get used over time as
anyone else with new programs and new terms, it's nice to know I can get =
a
template made exactly to my country and work with it...

For example, Tax names changes thru the countries, I think the standard n=
ame
is IVA, but one country is called IGV, in mine is ITBM, and so on...
Other terms that do change are related to "Spanglish".  In my country, th=
e
term "postear" is very commons since we had a strong influence with
Americans all over the place, so we have hacked the english/spanish langu=
age
more than most countries.
And about Spaniards, they do tend to call things in a very unique way tha=
t
sometimes even they don't like.

So, even though one spanish version seems like enough, maybe our users wi=
ll
not think the same.
So, how about we make sure the standard "es" template is the most correct=
 of
all as Antonio suggests, and we keep the country templates as a
customization template for our terms. ;)

Regards,
Gaby

-------------------------------------------------------------------------=
---
--
    Mantenimiento - Computadoras - Redes - Consultoria - Linux - Segurida=
d
-------------------------------------------------------------------------=
---
--
Tecno Parque Internacional, Edificio 218, Planta Baja, Clayton
Maria Gabriela Fong - Aptitudes, S.A.
mg...@ap...

Panama:   Apdo 87-2472, Zona 7, Panama
          Tel: +507-317-0145 / 46, Fax: +507-317-0145  [507 country code]

USA Mail: 1601 N.W. 97th Ave., PTY-823, Unit C-102, Miami, FL 33172, USA

----- Original Message -----
From: <ag...@ib...>
To: <sql...@li...>
Sent: Wednesday, May 16, 2001 5:13 PM
Subject: [SQL-Ledger-users] Spanish version


> Hi everybody!
>
> Please excuse me for this mail written in Spanish, but we want to find =
a
way to know how many spanish version of SQL-Ledger will exist.
>
> Estimados usuario de SQL-Ledger en Espa=F1ol:
>
> Recientemente se ha abierto una discusion acerca de la localizacion de
SQL-Ledger (SQLL) para cada pais de habla hispana.
>
> Esperando llegar a un acuerdo entre los hispano parlantes acerca de
cuantas versiones de SQLL existiran, escribo este mensaje.
>
> Actualmente existen dos opiniones:
>
> 1- Mantener una version unica de SQL-Ledger en espa=F1ol.
> 2- Crear una version especial para cada pais. (Actualmente esta es la
tendencia que lleva SQL-Ledger).
>
> Yo estoy de acuerdo con la primera opcion porque:
>
> 1-Aunque entiendo muy bien lo que son los regionalismos y particularida=
des
de cada pais. Creo que es muy bueno que podamos comunicarnos todos en el
mismo idioma.
>
> 2-No soy un experto en contabilidad, pero creo que entre los contadores=
 de
todos los paises hispanos utilizan los mismo terminos. (Apelo a los termi=
nos
correctos en espa=F1ol, no a los anglicismos empleados en algunos paises).
>
> 3-Por otro creo que la realidad lationamericana es un poco diferente de
Espa=F1a, seg=FAn lo planteado por el Eugenio en un correo enviado. Pero =
a nivel
latinoamericano se usan los mismos terminos. Debido a esto es posible que
pueda existir una version para Espa=F1a (Aunque tengo mis dudas).
>
> 4-La ventaja de mantener un solo lenguaje ahorra esfuerzos. En lugar de
utilizar esfuerzos en regionalizar para cada pais, podemos unir esfuerzos=
 y
mejorar la calidad de la documentacion en espa=F1ol.
>
> Bueno, estos son algunos de los motivos que tengo ahora en mente. Esper=
o
sus comentarios y les agradezco de antemano su colaboracion para hacer me=
jor
este sistema del que nos beneficiamos todos.
>
> Saludos,
>
> Ing. Antonio Gallardo
> AG Software
> Managua, NICARAGUA.
>
>
>

Compilation errors

[nyk <ny...@ru...>]

    I downloaded your SQL-Ledger 1.4.3 and trying to install onto my =
RedHat linux box running RedHat 6.2. There were no problems in getting =
the users created but when I wanted to login into the system, following =
message appears in my server error log:

Unknown error
Compilation failed in require at =
/home/paging2.easycall.com.my/htdocs/sql-ledger/login.pl line 61.
[Mon May 28 22:22:59 2001] [error] [client 172.1.1.20] Premature end of =
script headers: /home/paging2.easycall.com.my/htdocs/sql-ledger/login.pl

    Is there anything else that I have missed out in configuring the =
system? To my knowledge, I have correctly installed the DBD::Pg drivers =
as well as the DBI

    I appreciate if any help can be rendered.


Regards

Ng Yit Khuang
ny...@ru...

Help Please!

[Jess <je...@oz...>]

Hi People,
Could some kind sole send me the following in a tar or zip file from a
working system, Please?

The whole directory under:
    sql-ledger/bin

And these individual files.
    sql-ledger/admin.pl
    sql-ledger/login.pl
    sql-ledger/sql-ledger.conf


Where is setup/pl supposed to be, on what I have it is in the
"sql-ledger/bin" is this right?

Thankyou to those who can help.

I can't believe how much trouble I am having getting this to run.
I had no problem with the 1.2.* versions.

Regards Jess

Re: About Taxes

[Antonio G. <ag...@ib...>]

Dieter:

What about the payments?

Why we cannot use an account for payments. To track the history of when and
how much a customer pays or we pay to a provider.

Antonio Gallardo.


----- Original Message -----
From: "Dieter Simader" <dsi...@sq...>
To: <sql...@li...>
Sent: Monday, May 28, 2001 10:58 AM
Subject: About Taxes


> A brief overview how to set it all up and how it works.
>
> 1. Add an account in the chart of accounts.
>
> 2. check the box "Tax" if you want
>    Receivables -> a field to enter an amount in the receivables form
>    Payables -> a field to enter an amount in the payables form
>    Parts Inventory -> a checkbox with the description in the parts form to
> indicate that this part is taxable
>    Service Item -> a checkbox with the description in the service
> item form to indicate that the service is taxable
>
> 3. check "Yes" next to "Include this account on ..." if the account should
> be included on the customer / vendor forms to indicate that the customer /
> vendor is taxable at this level
>
> Repeat above for each tax you have. i.e if you have VAT @ 10, 14 and 30%
> add an account for each tax.
>
> 4. edit your preferences and enter a tax rate and tax number
>
>
> On an invoice the tax can either be included in the price or shown
> separately. If tax is included in the price the tax portion is not shown
> on the invoice. Taxes are only calculated if the customer/vendor is
> taxable at the same rate as the item. So, if a customer is taxable at VAT
> @ 10% and the item is set taxable at VAT @ 30% no taxes will be
> calculated. You must also indicate that the customer is taxable at VAT @
> 30%.
>
> Taxes are calculated differently if included in price or shown on top.
> i.e.  $100 item, taxable at 7%
>  tax included -> net price is 93.46, tax portion is 6.54
>  tax on top -> net price is 100.00, tax is 7.00
>
> multiple taxes are always additive and not calculated tax on tax.
> So, the same $100 item at 7% and 8%
>  tax included -> net price is 86.96, tax is 13.04
>  tax on top -> net price is 100.00, tax is 15.00
>
>
> 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 ===========
>
>
>

About Taxes

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

A brief overview how to set it all up and how it works.

1. Add an account in the chart of accounts.

2. check the box "Tax" if you want
   Receivables -> a field to enter an amount in the receivables form
   Payables -> a field to enter an amount in the payables form
   Parts Inventory -> a checkbox with the description in the parts form to
indicate that this part is taxable
   Service Item -> a checkbox with the description in the service
item form to indicate that the service is taxable

3. check "Yes" next to "Include this account on ..." if the account should
be included on the customer / vendor forms to indicate that the customer /
vendor is taxable at this level

Repeat above for each tax you have. i.e if you have VAT @ 10, 14 and 30%
add an account for each tax.

4. edit your preferences and enter a tax rate and tax number


On an invoice the tax can either be included in the price or shown
separately. If tax is included in the price the tax portion is not shown
on the invoice. Taxes are only calculated if the customer/vendor is
taxable at the same rate as the item. So, if a customer is taxable at VAT
@ 10% and the item is set taxable at VAT @ 30% no taxes will be
calculated. You must also indicate that the customer is taxable at VAT @
30%.

Taxes are calculated differently if included in price or shown on top.
i.e.  $100 item, taxable at 7%
 tax included -> net price is 93.46, tax portion is 6.54
 tax on top -> net price is 100.00, tax is 7.00

multiple taxes are always additive and not calculated tax on tax.
So, the same $100 item at 7% and 8%
 tax included -> net price is 86.96, tax is 13.04
 tax on top -> net price is 100.00, tax is 15.00


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 ===========

Re: Problems running SQL Ledger 1.4.3

[Jess <je...@oz...>]

Hi,

Yes that was done at the beginning.

The perl files in the "bin/mozilla/*.pl" they don't have the shebang line at
the top of the source code and are missing the require "sql-ledger.conf";

Is this normal?

Also if you look at the error log file down below it says something about::
"Premature end of script headers: /www/sqll/login.pl"

What is that about?

Regards Jess


----- Original Message -----
From: "Antonio Gallardo" <ag...@ib...>
To: <sql...@li...>
Sent: Monday, 28 May, 2001 4:29 PM
Subject: Re: Problems running SQL Ledger 1.4.3


> You must remove the password before start.
>
> I think this will be on the members directory.
>
> Please, check the upgrade procedure.
>
> Regads,
>
> Antonio
> ----- Original Message -----
> From: "Jess" <je...@oz...>
> To: <sql...@li...>
> Sent: Sunday, May 27, 2001 9:50 PM
> Subject: Re: Problems running SQL Ledger 1.4.3
>
>
> >
> > Hi List Members,
> > I have done a clean install of 1.4.3.
> > I was using 1.2.10 of SQL Ledger without any problems.  So I didn't
bother
> > going through upgrading procedure I didn't have anything of value in the
> > database so I instead just wiped the tables and rebuilt them with
> > "acc-Pg.sql" and then copied all the files to the same folder the 1.2.10
> > version was in after I deleted version 1.2.10 files from the web root
> > subdirectory called "SQLL" in lower case.
> >
> > When I run http://192.168.1.3/sqll/login.pl
> >
> > I get the login screen, I type in "Username" as in the "admin/members"
> file
> > and no password and I get:
> >
> > ============>>>>>>>>>>
> > Internal Server Error
> > The server encountered an internal error or misconfiguration and was
> unable
> > to complete your request.
> > Please contact the server administrator, me...@oz... and inform
them
> of
> > the time the error occurred, and anything you might have done that may
> have
> > caused the error.
> > More information about this error may be available in the server error
> log.
> >
> > Apache/1.3.14 Server at 192.168.1.4 Port 80
> > ========>>>>>>>>>>>>>>>>
> >
> > Access Log:---
> > [Mon May 28 13:08:26 2001] [error] [client 192.168.1.3] Premature end of
> > script headers: /www/sqll/login.pl
> > [Mon May 28 13:20:51 2001] [error] [client 192.168.1.3] Premature end of
> > script headers: /www/sqll/login.pl
> > Error Log:---
> > 192.168.1.3 - - [28/May/2001:13:08:14 +1000] "GET /sqll/login.pl
HTTP/1.1"
> > 200 1087
> > 192.168.1.3 - - [28/May/2001:13:08:19 +1000] "POST /sqll/login.pl
> HTTP/1.1"
> > 200 121
> > 192.168.1.3 - - [28/May/2001:13:08:26 +1000] "POST /sqll/login.pl
> HTTP/1.1"
> > 500 604
> > 192.168.1.3 - - [28/May/2001:13:20:51 +1000] "POST /sqll/login.pl
> HTTP/1.1"
> > 500 604
> >
> >
> > What is it I am missing?
> >
> > Regards Jess
> >
> > My setup:
> > Win2000 Professional
> > Apache 1.3.14
> > Lastest Perl
> > PostreSQL 7.0.3
> >
> >
> >
> >
> >
>
>
>

Re: Problems running SQL Ledger 1.4.3

[Antonio G. <ag...@ib...>]

You must remove the password before start.

I think this will be on the members directory.

Please, check the upgrade procedure.

Regads,

Antonio
----- Original Message -----
From: "Jess" <je...@oz...>
To: <sql...@li...>
Sent: Sunday, May 27, 2001 9:50 PM
Subject: Re: Problems running SQL Ledger 1.4.3


>
> Hi List Members,
> I have done a clean install of 1.4.3.
> I was using 1.2.10 of SQL Ledger without any problems.  So I didn't bother
> going through upgrading procedure I didn't have anything of value in the
> database so I instead just wiped the tables and rebuilt them with
> "acc-Pg.sql" and then copied all the files to the same folder the 1.2.10
> version was in after I deleted version 1.2.10 files from the web root
> subdirectory called "SQLL" in lower case.
>
> When I run http://192.168.1.3/sqll/login.pl
>
> I get the login screen, I type in "Username" as in the "admin/members"
file
> and no password and I get:
>
> ============>>>>>>>>>>
> Internal Server Error
> The server encountered an internal error or misconfiguration and was
unable
> to complete your request.
> Please contact the server administrator, me...@oz... and inform them
of
> the time the error occurred, and anything you might have done that may
have
> caused the error.
> More information about this error may be available in the server error
log.
>
> Apache/1.3.14 Server at 192.168.1.4 Port 80
> ========>>>>>>>>>>>>>>>>
>
> Access Log:---
> [Mon May 28 13:08:26 2001] [error] [client 192.168.1.3] Premature end of
> script headers: /www/sqll/login.pl
> [Mon May 28 13:20:51 2001] [error] [client 192.168.1.3] Premature end of
> script headers: /www/sqll/login.pl
> Error Log:---
> 192.168.1.3 - - [28/May/2001:13:08:14 +1000] "GET /sqll/login.pl HTTP/1.1"
> 200 1087
> 192.168.1.3 - - [28/May/2001:13:08:19 +1000] "POST /sqll/login.pl
HTTP/1.1"
> 200 121
> 192.168.1.3 - - [28/May/2001:13:08:26 +1000] "POST /sqll/login.pl
HTTP/1.1"
> 500 604
> 192.168.1.3 - - [28/May/2001:13:20:51 +1000] "POST /sqll/login.pl
HTTP/1.1"
> 500 604
>
>
> What is it I am missing?
>
> Regards Jess
>
> My setup:
> Win2000 Professional
> Apache 1.3.14
> Lastest Perl
> PostreSQL 7.0.3
>
>
>
>
>

Re: Problems running SQL Ledger 1.4.3

[Jess <je...@oz...>]

Hi List Members,
I have done a clean install of 1.4.3.
I was using 1.2.10 of SQL Ledger without any problems.  So I didn't bother
going through upgrading procedure I didn't have anything of value in the
database so I instead just wiped the tables and rebuilt them with
"acc-Pg.sql" and then copied all the files to the same folder the 1.2.10
version was in after I deleted version 1.2.10 files from the web root
subdirectory called "SQLL" in lower case.

When I run http://192.168.1.3/sqll/login.pl

I get the login screen, I type in "Username" as in the "admin/members" file
and no password and I get:

============>>>>>>>>>>
Internal Server Error
The server encountered an internal error or misconfiguration and was unable
to complete your request.
Please contact the server administrator, me...@oz... and inform them of
the time the error occurred, and anything you might have done that may have
caused the error.
More information about this error may be available in the server error log.

Apache/1.3.14 Server at 192.168.1.4 Port 80
========>>>>>>>>>>>>>>>>

Access Log:---
[Mon May 28 13:08:26 2001] [error] [client 192.168.1.3] Premature end of
script headers: /www/sqll/login.pl
[Mon May 28 13:20:51 2001] [error] [client 192.168.1.3] Premature end of
script headers: /www/sqll/login.pl
Error Log:---
192.168.1.3 - - [28/May/2001:13:08:14 +1000] "GET /sqll/login.pl HTTP/1.1"
200 1087
192.168.1.3 - - [28/May/2001:13:08:19 +1000] "POST /sqll/login.pl HTTP/1.1"
200 121
192.168.1.3 - - [28/May/2001:13:08:26 +1000] "POST /sqll/login.pl HTTP/1.1"
500 604
192.168.1.3 - - [28/May/2001:13:20:51 +1000] "POST /sqll/login.pl HTTP/1.1"
500 604


What is it I am missing?

Regards Jess

My setup:
Win2000 Professional
Apache 1.3.14
Lastest Perl
PostreSQL 7.0.3

Re: Problems getting my site up...;-(

[John C. N. y L. <nj...@nt...>]

> 
> Did you install DBD-Pg?  Doesn't look to me like it comes with
> Mandrake.

Uhhh no...;-)  Installed it and it work...;-)  Yeah yeah I know..  Read
the FAQ...;-)

Thanks.


Cheers,


John Clark

-- 
     /) John Clark Naldoza y Lopez                           (\
    / )    Software Design Engineer II                       ( \
  _( (_    _  Web-Application Development                    _) )_
 (((\ \>  /_>    Cable Modem Network Management System <_\  </ /)))
 (\\\\ \_/ /         NEC Telecom Software Phils., Inc.  \ \_/ ////)
  \       /                                              \       /
   \    _/  phone: (+63 32) 233-9142 loc. 3112            \_    /
   /   /  cellphone: (+63 919) 399-4742                     \   \
  /   / email: nj...@nt...                        \   \

Re: tax

[adrian <ad...@sn...>]

Dieter Simader wrote:
> 
> The field is used for a tax number.
> 
> Usually when you charge tax this number must appear somewhere on an
> invoice. To place the number on your invoice use the template tag
> <%taxnumber%>
> 

OK in Australia there is generally no number as it is GST (or VAT).

In the upgrade instructions what is the customertax table, vendortax
table and partstax table ?

Adrian

Re: tax

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

The field is used for a tax number.

Usually when you charge tax this number must appear somewhere on an
invoice. To place the number on your invoice use the template tag
<%taxnumber%>


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 Wed, 23 May 2001, adrian wrote:

> Setting up of preferences, Tax Accounts
> 
> Rate (%) say 10
> 
> Number   what does this refer to ?
> 
> Adrian
> 
> 

Re: Problems getting my site up...;-(

[Rod R. <ro...@su...>]

On Tuesday 22 May 2001 17:45, John Clark Naldoza y Lopez wrote:
> Rod Roark wrote:
> > I got this when I upgraded PostgreSQL.  Rebuilding and
> > reinstalling DBI and DBD fixed it for me, though I'm sure other
> > causes are possible.
>
> Thanks for the info...  But I kinda installed everything from
> Mandrake 8.0...  Fresh install type of thing...;-(

Did you install DBD-Pg?  Doesn't look to me like it comes with 
Mandrake.

-- Rod
   http://www.sunsetsystems.com/

Re: Problems getting my site up...;-(

[John C. N. y L. <nj...@nt...>]

Rod Roark wrote:
> 
> I got this when I upgraded PostgreSQL.  Rebuilding and reinstalling
> DBI and DBD fixed it for me, though I'm sure other causes are possible.
> 

Thanks for the info...  But I kinda installed everything from Mandrake
8.0...  Fresh install type of thing...;-(


Cheers,


John Clark


-- 
     /) John Clark Naldoza y Lopez                           (\
    / )    Software Design Engineer II                       ( \
  _( (_    _  Web-Application Development                    _) )_
 (((\ \>  /_>    Cable Modem Network Management System <_\  </ /)))
 (\\\\ \_/ /         NEC Telecom Software Phils., Inc.  \ \_/ ////)
  \       /                                              \       /
   \    _/  phone: (+63 32) 233-9142 loc. 3112            \_    /
   /   /  cellphone: (+63 919) 399-4742                     \   \
  /   / email: nj...@nt...                        \   \

tax

[adrian <ad...@sn...>]

Setting up of preferences, Tax Accounts

Rate (%) say 10

Number   what does this refer to ?

Adrian

Re: Problems getting my site up...;-(

[Rod R. <ro...@su...>]

I got this when I upgraded PostgreSQL.  Rebuilding and reinstalling 
DBI and DBD fixed it for me, though I'm sure other causes are possible.

-- Rod

On Tuesday 22 May 2001 01:35, John Clark Naldoza y Lopez wrote:
> Hi,
>
>
> I've been trying for the past few days to get my SQL-Ledger
> Running.. But I keep getting this error after I login
>
> ---------< WHOLE PAGE >----------------
>
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was
> unable to complete your request.
>
> Please contact the server administrator, nj...@nt... and
> inform them of the time the error occurred, and anything you might
> have done that may have caused the
> error.
>
> More information about this error may be available in the server
> error log.
> ---------------------------------------
>
>
> When I check my error log this is what I got...
>
> Unknown error
> Compilation failed in require at /usr/sql-ledger/login.pl line 61.
> [Tue May 22 16:19:30 2001] [error] [client 172.28.59.157] Premature
> end of script headers: /usr/sql-ledger/login.pl
>
> By check like 61 this is what I found
>
> require "$form{path}/$script";
>
> -----------
>
> Am I missing something???
>
> Any help would be highly appreciated.
>
>
> Cheers,
>
>
> John Clark

Problems getting my site up...;-(

[John C. N. y L. <nj...@nt...>]

Hi,


I've been trying for the past few days to get my SQL-Ledger Running.. 
But I keep getting this error after I login

---------< WHOLE PAGE >----------------

Internal Server Error

The server encountered an internal error or misconfiguration and was
unable to complete your request.

Please contact the server administrator, nj...@nt... and
inform them of the time the error occurred, and anything you might have
done that may have caused the
error.

More information about this error may be available in the server error
log.
---------------------------------------


When I check my error log this is what I got...

Unknown error
Compilation failed in require at /usr/sql-ledger/login.pl line 61.
[Tue May 22 16:19:30 2001] [error] [client 172.28.59.157] Premature end
of script headers: /usr/sql-ledger/login.pl

By check like 61 this is what I found

require "$form{path}/$script"; 

-----------

Am I missing something???

Any help would be highly appreciated.


Cheers,


John Clark

-- 
     /) John Clark Naldoza y Lopez                           (\
    / )    Software Design Engineer II                       ( \
  _( (_    _  Web-Application Development                    _) )_
 (((\ \>  /_>    Cable Modem Network Management System <_\  </ /)))
 (\\\\ \_/ /         NEC Telecom Software Phils., Inc.  \ \_/ ////)
  \       /                                              \       /
   \    _/  phone: (+63 32) 233-9142 loc. 3112            \_    /
   /   /  cellphone: (+63 919) 399-4742                     \   \
  /   / email: nj...@nt...                        \   \

Re: Parse error

[Antti K. <aka...@si...>]

> Version 1.4

> In trying to add or modify an account that includes tax for parts or
> services I get the following error :

> " ERROR: parser: parse error at or near ","   "

I pointed this out for Dieter and I think he fixed it in post-1.4.0
versions.

The bug was in SL/Admin.pm, at the end of sub save_account, where
$chart_id will always be empty when SQL "INSERT INTO tax (chart_id,
rate) VALUES ($chart_id, 0)" is executed. I fixed this by replacing
$chart_id here with $form->{id}, but I think Dieter had a more beautiful
fix for this.

---------------------------------------
Antti Kaihola
Ambitone Oy, Helsinki, Finland

Päivän palindromi: "Kas, iso luottamus. Asu: Matto. Ulos, Isak!"

Parse error

[adrian <ad...@sn...>]

Version 1.4

In trying to add or modify an account that includes tax for parts or
services I get the following error :

" ERROR: parser: parse error at or near ","   "

Anyone else with the same problem?  Any ideas as to why?

Adrian

Sales Tax ??

[Rodney <ro...@ra...>]

Okay, I know I must just be confused on how this works now. I upgraded
from the 1.2.x to 1.4.2 and how does the sales tax work on invoices. It
use to have a section in the setup to add the % and the it would
automatically be added to taxable parts, but now it seems to be
different. I do not see were to change tax % and for it to be added. I se=
e
some check make for tax included, but what is this. I want it to be added
automatically to taxable parts.=20


    \\\|||///
    \ ~=A0=A0 ~ /
    | @   @ |
-oOo---(_)---oOo-----------------------------------------------

	RAM Technical
	Rodney Mosley
	Systems Administration
	E-Mail:ro...@ra...
	http://www.ramnic.com

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
	Check out http://www.setfree.org It can change your life.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Confused about links

[Rod R. <ro...@su...>]

I just installed sql-ledger 1.4.2 on a Slackware box -- it's been a 
while since I last looked at it and I'm very impressed with its 
progress.

Here's my question: what is the "Link" column for in the 
chart-of-accounts list, and what sets its value?  Also when I add a 
part or service, what roles will the "Link Accounts" choices play?

Thanks...

-- Rod

Re: [SQL-Ledger-users] PHP version of sql-ledger

[ivan <iva...@42...>]

On Sun, May 13, 2001 at 10:42:17PM -0500, Linas Vepstas wrote:
> On Sun, May 13, 2001 at 12:39:26PM -0400, Michael Diehl was heard to remark:
> > 
> > PHP works like ASP or JSP so that you can include PHP code in your HTML
> > page,  it just has top be escaped with <?PHP ... your code... ?>. 
> > So it fits more with the most popular way of doing things at the moment.
> > When you are using templates, this becomes a bit meaningless, of course.
> > (And you can integrate Perl into the server as well)
> 
> FYI, 'eperl' by ralf engelschall does the same thing for perl.
> It was recently converted to an apache module (mod_eperl, I beleive).
> I think the escape is <? but I think <: also works ... 

eperl is not well-maintained (the most recent release is from 1998 and
does not work with perl 5.005 or 5.6) and most of the userbase has moved
on to more current templating packages. 

In the "little language" category, Embperl and Template Toolkit are
popular, maintained choices, while in the "eval" category, HTML::Mason and
Apache::ASP are maintained and widely used.

-- 
meow
_ivan

Re: [SQL-Ledger-users] Q. on the TO-DO list. (Payroll update)

[Izzy B. <iz...@ec...>]

At 01:57 PM 10/05/01, you wrote:
>On Thu, May 10, 2001 at 03:23:21PM -0400, Wayne was heard to remark:
> > Hi  Steve,
> > This book has good data model for  a business.
> > One enity that is present is a "Party", a party is
> > a person or and organization. One then associates
> > a relationship to a "Party". This will help to reduce
> > data redundancy. For example, if I have an employee
> > that happens to be a vendor, then the party is in
> > my DB only once , as a person, and I only have to
> > establish the relationship this enity has. That
>
>Bad example.
>
>If you have employees who also act as vendors to you,
>you are putting yourself into a conflict of interest.
>If you're the sole owner, hey, that's up to you, but
>if you work for a larger company, that's grounds for
>getting yourself and your employee fired.   If the
>employee is paying you kickbacks, I think that may
>even be a felony under rico.
>
>--linas
>
>--
>Linas Vepstas -- li...@gn... -- http://www.gnumatic.com/

This of course depends on the situation.  I for one work in co-operation 
with people who are in fact my competitors.  I trust them only as far as I 
need to, but they purchase my products and services as I do theirs.  In 
this regard they are both a vender and a customer.  A more common situation 
is for employees to purchase the products of their employer.  The concept 
expressed is still the same.  There are certain characteristics of venders, 
customers, and employees which are all the same.  Creating multiple tables 
to track the same things doesn't make a lot of sense in all situations.

Of course in your situation, there may be very good reasons to keep this 
data in separate tables.  Maybe you already have an existing vender 
database which tacks the venders address info.  In this case your need to 
keep the existing system will outweigh the need to reduce duplication.  My 
suggestion of building SQL-Ledger around the idea of being able to replace 
all none accounting specific modules with customer/country specific 
versions would allow SQL-Ledger to meet both needs. SQL-Ledger doesn't need 
to track Venders internally.  Just transactions with venders.

...Izzy

Re: [SQL-Ledger-users] Q. on the TO-DO list. (Payroll update)

[Izzy B. <iz...@ec...>]

At 01:23 PM 10/05/01, you wrote:
>Hi  Steve,
>I was going to hold off on offering some suggestion
>until I understand what is going on in the code, but
>if anyone is going to develope the payroll I would
>suggest that we look at the data model a little further.
>The suggertion I'm going to make is not my own. If
>folks like to purchase the book "The Data Model
>Resource Book"  ISBN 0-471-15364-8
>you can see where I'm coming from.
>This book has good data model for  a business.
>One enity that is present is a "Party", a party is
>a person or and organization. One then associates
>a relationship to a "Party". This will help to reduce
>data redundancy. For example, if I have an employee
>that happens to be a vendor, then the party is in
>my DB only once , as a person, and I only have to
>establish the relationship this enity has. That
>relationship would be "employee" and  "vendor".
>I know I'm leaving alot of description out, but
>I think if people purchase the book it would give
>the group a good model to follow.

I was thinking along the same lines.  Thanks for the suggestion of the 
book.  I'll see if I can find it.  My thoughts on it were that it doesn't 
make sense to have multiple address databases.  An employee can be a 
customer as well as a vender and so on.  It's also worth noting that 
contact info isn't always unique.  Multiple people can live or work at the 
same location and have the same phone numbers.  Of course there's always a 
performance trade off between keeping redundant/duplicate information or 
doing multiple table lookups.

IMHO, SQL-Ledger should be flexible enough to take advantage of whichever 
contact manager, inventory control system, invoice system, payroll system, 
etc, that makes the most sense for a given customer and a given 
location.  I don't believe that it makes sense to tightly integrate a whole 
bunch of features and functions into SQL-Ledger.  A more modular approach 
that lets the developer for a given customer decide what  modules to use is 
what I'm after.  SQL-Ledger should concentrate on the accounting side of 
things and that's it.  Everything else belongs in a different project that 
can be linked in with the appropriate glue logic.

Every industry is different and has different unique needs.  For instance, 
a moving company needs to keep track of at least two addresses for every 
person; their old address and their new address. It doesn't make sense to 
integrate a contact manager into SQL-Ledger that can only handle one 
address.  Nor does it make sense to integrate a contact manager that can 
handle two addresses.  The ideal solution would be to develop SQL-Ledger 
with the idea that contact management is the responsibility of a different 
program and only store a reference to a given contact in the SQL-Ledger 
tables.  A well defined interface could then be created to allow the front 
end to extract the required data from which ever contact manager makes the 
most sense for a given customer. Creating, modifying, or deleting contacts 
should be passed of to the contact manager's interface.

I'm not saying that we don't want to create a feature rich accounting 
package here.  On the contrary, I think that the more features we can give 
it, the more likely business will consider it a viable option.  I just 
think that thought and planning should go into building each module in such 
a way that it can be replaced with an industry/country specific version as 
needed.  In that way we aren't needlessly bloating SQL-Ledger in an effort 
to make it meet the needs of everyone.  Creating basic, general purpose 
modules that are replaceable is the only way to go, IMHO.

 From the point of view of the payroll system, I think that the SQL-Ledger 
tables should be limited to tracking an employee ref#, pay cheque amount, 
and deductions.  If it isn't AP/AR/GL related, it doesn't need to be in the 
SQL-Ledger tables.  A Perl package should be created that will give a 
developer the necessary functions to interface with these tables as 
needed.  i.e. add new entires to the payroll table as cheques are being 
printed.  There's no need for SQL-Ledger to get involved in tracking 
vacation days, sick days, start date, and termination dates of 
employees.  This is clearly not accounting related but would be a part of 
any good employee tracking system.  Even the functions of printing cheques, 
tracking hours, over time tracking, pay rates, etc aren't really accounting 
related.  Just the amount paid and deducted are.

If we all think in this way when we develop new , or overhauling old 
features for SQL-Ledger, then we'll have a much richer accounting package 
in the end that can meet the needs of everyone without becoming excessively 
bloated in the process.

...Izzy


>Later.
>Wayne
>P.S. I should also point out that I'm learning Perl
>to convert the system to Python. I hope that
>doesn't offend anyone.


No offence here.  I'd actually planned and started to learn Python before 
taking up Perl.  Because of my intention to participate in developing 
SQL-Ledger, I decided to take up Perl first.  I've since learned the 
basics.  I wont insult anyone by suggesting I've become an expert in the 
short time I've been playing with it, but I know enough to be able to read 
the code and understand what is going on now.  I'd be very interested in 
looking at a Python port though.  If nothing else, it may aid my learning 
of Python! :)


>Steve Doerr wrote:
>
> > Hi Wayne/everybody.
> >
> > Wayne wrote:
> >
> > > Hello,
> > > I see on the TO-DO list that  Steve has started
> > > a payroll system and Roderick has started  aging
> > > reports. Are these avaiable to view?
> > > Thanks.
> > > Wayne.
> >
> > I started a payroll system and there isn't anything that can be loaded
> > or used yet.  If anyone wants to help or has any input on it, please let
> > me know and I'll send you what I have.  I've got an employee package and
> > a few of the sql tables started.
> >
> > Here's what I have planned - it's a three part system and it just
> > follows existing forms and modules.
> >
> > 1.  An entry form and perl module to set up an employee's information
> > (i.e. name, address, pay rate, withholdings/deductions).  This is going
> > to write each employee's info to the database, which will be called and
> > applied to their pay period data when you enter and run payroll.  I've
> > got a separate table for deductions/withholdings that will have a two
> > part id, one associates them with an employee id and one numbers them.
> > It should be able to hold an infinite number and types of deductions for
> > employees in any country (that's the goal).
> >
> > 2.  An entry form and perl module to enter each employee's data for the
> > pay period (hours worked, vacation taken, sick time taken, etc.).
> > You'll also be able to run and post the pay period data here.
> >
> > 3. Reports.
> >
> > That's a brief overview of payroll.
> > Steve