sql-ledger-users — SQL-Ledger users

no login for users

[Johan v. R. <jv...@nl...>]

Hello,

I seam to have some problems to login sql-ledger as a user.

All goes well when i connect to the "server".
I am able to creat user and databases. 
but i can not login as a user whith login.pl
Nothing happends and no messages when i type in the name and passwd.

 Whats wrong 

-- 
Johan

SQL-Ledger and NT

[Bill H. <bil...@fa...>]

I just recently discovered SQL-Ledger.  I currently run NT4, and I've
downloaded the cygwin utilities.  

On the SQL-Ledger pages, I see mention of a way to use it under W2K. 
Have people successfully installed and run SQL-Ledger under NT4?  I'm
not a PERL programmer, nor have I used postgresql before, so I have a
bit of a learning curve, but it seems easier to use and more capable
than BANAL.  Tips welcome.

Thanks,

Bill
-- 
Bill Harris                                  3217 102nd Place SE
Facilitated Systems                          Everett, WA 98208 USA
http://facilitatedsystems.com/               phone: +1 425 337-5541

Re: Security, and Including Labor on Assemblies....

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

Hi David,

Add the next two lines to IS.pm after line 350

    $ref->{inventory_accno_id} *= 1;
    $ref->{expense_accno_id} *= 1;

and change $allocated in the else condition to

      $allocated = &allocate_expense($dbh, $form, $ref->{parts_id},
$ref->{qty}) if ($ref->{inventory_accno_id});


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, 14 Nov 2001, David Ratte wrote:

> Gentlemen (and ladies...)
> 
> Two brief questions:
> 1. One of my last concerns before my all-out switch to sql-ledger is about 
> security... my concern is that since password protection on each page 
> consists only of having a valid username attached on the end of the url, a 
> terminated employee can still access the system as long as he/she still knows 
> the name of anyone who works here.
> 
> All they have to do us add:
>  http://URL?path=bin/mozilla&action=xxx&login=StillEmployedUserName
> 
> So my questions is this (yes it takes me a while to get to the point!):
> Is it possible to use some form of a SESSION ID instead, such that after a 
> successful login the path becomdes URL?session=XNCBXNBC&action=xxx
> 
> This way the sessions can expire at some interval (hourly, daily, etc) and 
> the slightly more crafty user is defeated.
> 
> 2. I have a question about how to include LABOR in an ASSEMBLY. Here is what 
> I did - and hopefully someone has a better way/workaround.
> 
> I have a service item that is called LABOR and its measured in minutes. I 
> would like to include it on the Bill of Materials, because for each assembly 
> it is a fixed average time. This way, the computed price for the assembly is 
> accurate, reflecting materials and labor for an assembly.
> 
> Here's the glitch... since a SERVICE is not a PART it does not have an 
> INVENTORY ACCOUNT. You can attach the service to a BOM, but when you try to 
> invoice the assembly, you cannot post the invoice because the post query 
> fails (due to the lack of the inventory account)
> 
> One possible workaround, would be to make TIME a PART, but then at the end of 
> the week there is an inventory shortage of MINUTES and adjusting that all the 
> time could become a nightmare.
> 
> Any ideas on either topic appreciated.
> Thanks,
> Dave Ratte
> dr...@su...
> 
> 

Re: Security, and Including Labor on Assemblies....

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

You can use apache mod_perl authentication/session modules... rather
than rewrite the sql-ledger code. Some purists argue about where
authentication and session management code should sit in multi-tiered
architectures... I think just do it where you feel most
comfortable. You can always deal with the consequences later. ;-)

On Thursday, 2001-11-15 at 02:18:15 AM, David Ratte scribbled:
> Gentlemen (and ladies...)
> 
> Two brief questions:
> 1. One of my last concerns before my all-out switch to sql-ledger is about 
> security... my concern is that since password protection on each page 
> consists only of having a valid username attached on the end of the url, a 
> terminated employee can still access the system as long as he/she still knows 
> the name of anyone who works here.
> 
> All they have to do us add:
>  http://URL?path=bin/mozilla&action=xxx&login=StillEmployedUserName
> 
> So my questions is this (yes it takes me a while to get to the point!):
> Is it possible to use some form of a SESSION ID instead, such that after a 
> successful login the path becomdes URL?session=XNCBXNBC&action=xxx
> 
> This way the sessions can expire at some interval (hourly, daily, etc) and 
> the slightly more crafty user is defeated.



-- 
Benjamin Lee
Melbourne, Australia             "Always real."    http://realthought.net/

Weather outside looks to be 11.4°C, partly cloudy.
__________________________________________________________________________
Base 8 is just like base 10, if you are missing two fingers.
		-- Tom Lehrer

Security, and Including Labor on Assemblies....

[David R. <dr...@su...>]

Gentlemen (and ladies...)

Two brief questions:
1. One of my last concerns before my all-out switch to sql-ledger is about 
security... my concern is that since password protection on each page 
consists only of having a valid username attached on the end of the url, a 
terminated employee can still access the system as long as he/she still knows 
the name of anyone who works here.

All they have to do us add:
 http://URL?path=bin/mozilla&action=xxx&login=StillEmployedUserName

So my questions is this (yes it takes me a while to get to the point!):
Is it possible to use some form of a SESSION ID instead, such that after a 
successful login the path becomdes URL?session=XNCBXNBC&action=xxx

This way the sessions can expire at some interval (hourly, daily, etc) and 
the slightly more crafty user is defeated.

2. I have a question about how to include LABOR in an ASSEMBLY. Here is what 
I did - and hopefully someone has a better way/workaround.

I have a service item that is called LABOR and its measured in minutes. I 
would like to include it on the Bill of Materials, because for each assembly 
it is a fixed average time. This way, the computed price for the assembly is 
accurate, reflecting materials and labor for an assembly.

Here's the glitch... since a SERVICE is not a PART it does not have an 
INVENTORY ACCOUNT. You can attach the service to a BOM, but when you try to 
invoice the assembly, you cannot post the invoice because the post query 
fails (due to the lack of the inventory account)

One possible workaround, would be to make TIME a PART, but then at the end of 
the week there is an inventory shortage of MINUTES and adjusting that all the 
time could become a nightmare.

Any ideas on either topic appreciated.
Thanks,
Dave Ratte
dr...@su...

Re: document contains no data

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

Did you load admin.pl and setup a user?

I assume you use cjs as your login name into your computer and created a
database cjs and the tables under your name.

Load admin.pl and click on *Add User*,
Enter cjs as login
In the Database section enter cjs in the Name and User field
Leave the Host and Port field empty.


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, 13 Nov 2001, cjs wrote:

> I have everything set up for sql-ledger and all seems ok, except I
> cannot login. I get the message that the document contains no data. I am
> using the server that came with sql-ledger, and set up the tables and
> charts by hand as in the readme instructions. I created the database by
> hand as well and postmaster runs fine. Can anyone tell me where to go
> next? I have tried putting the database files in a number of different
> directories but no luck. Thanks so much.
> 
> 

document contains no data

[cjs <cj...@pa...>]

I have everything set up for sql-ledger and all seems ok, except I
cannot login. I get the message that the document contains no data. I am
using the server that came with sql-ledger, and set up the tables and
charts by hand as in the readme instructions. I created the database by
hand as well and postmaster runs fine. Can anyone tell me where to go
next? I have tried putting the database files in a number of different
directories but no luck. Thanks so much.

Re: Working with Accounts Payable

[<ga...@es...>]

Dieter,

Thanks for the inforamtion and the suggestion.  This will work.  It is a
great starting point.  I just wanted to make sure I understood how it was
suppose to work so I could set up a system that works as well as possiable.

	-Gary


At 11:32 AM 11/10/2001 -0700, Dieter Simader wrote:
>Enter a description in the Invoice Number field. The field is not a number
>and you can enter anything you like.
>
>PST = Provincial Sales Tax.
>
>The default chart of accounts is a *starting point* and by no means a
>solution for everyone. Change it to your needs.
>
>
>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 Sat, 10 Nov 2001 ga...@es... wrote:
>
>> 
>> Hello,
>> 
>> I'm setting up SQL-Ledger and I'm confused about how best to use it.  I've
>> figured out Accounts Recievable, but I don't think I've figured out the
>> best way to work with Accounts Payable.  Here is the issue.
>> 
>> Lets say that I have a phone bill that I want to enter.  The logical thing
>> to do is to create a Vendor Invoice.  This requires a part number and I
>> don't want to create parts for things like phone bills.  So I go to Add
>> Transaction.  Entering it here will work although it has no description so
>> I can go back later and figure out exactly what it was for.  Also, it
>> doesn't provide an invoice number which means I have to be careful to add
>> my own unique one.  I think I'm not using the tools provided correctly,
>> because things aren't working seamlessly.  Someone elses input would be
>> helpful.
>> 
>> Also, what is PST?  When I see it I think Pacific Standard Time =-)
>> 
>> 	-Gary
>> 
>> 
>> 
>> 
>> 
>
>
>
>

Re: Working with Accounts Payable

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

Enter a description in the Invoice Number field. The field is not a number
and you can enter anything you like.

PST = Provincial Sales Tax.

The default chart of accounts is a *starting point* and by no means a
solution for everyone. Change it to your needs.


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 Sat, 10 Nov 2001 ga...@es... wrote:

> 
> Hello,
> 
> I'm setting up SQL-Ledger and I'm confused about how best to use it.  I've
> figured out Accounts Recievable, but I don't think I've figured out the
> best way to work with Accounts Payable.  Here is the issue.
> 
> Lets say that I have a phone bill that I want to enter.  The logical thing
> to do is to create a Vendor Invoice.  This requires a part number and I
> don't want to create parts for things like phone bills.  So I go to Add
> Transaction.  Entering it here will work although it has no description so
> I can go back later and figure out exactly what it was for.  Also, it
> doesn't provide an invoice number which means I have to be careful to add
> my own unique one.  I think I'm not using the tools provided correctly,
> because things aren't working seamlessly.  Someone elses input would be
> helpful.
> 
> Also, what is PST?  When I see it I think Pacific Standard Time =-)
> 
> 	-Gary
> 
> 
> 
> 
> 

Working with Accounts Payable

[<ga...@es...>]

Hello,

I'm setting up SQL-Ledger and I'm confused about how best to use it.  I've
figured out Accounts Recievable, but I don't think I've figured out the
best way to work with Accounts Payable.  Here is the issue.

Lets say that I have a phone bill that I want to enter.  The logical thing
to do is to create a Vendor Invoice.  This requires a part number and I
don't want to create parts for things like phone bills.  So I go to Add
Transaction.  Entering it here will work although it has no description so
I can go back later and figure out exactly what it was for.  Also, it
doesn't provide an invoice number which means I have to be careful to add
my own unique one.  I think I'm not using the tools provided correctly,
because things aren't working seamlessly.  Someone elses input would be
helpful.

Also, what is PST?  When I see it I think Pacific Standard Time =-)

	-Gary

Re: unable to access sql-ledger

[Steve D. <sd...@sw...>]

Leave it blank and enter it.  That's the user setup screen.  The main
program is accessed thru login.pl.

cjs wrote:

> I am running sus 7.1. I installed all the requisite packages for sql,
> dbi, etc...
> All went well. I installed sql-ledger, no problem. I am using the server
> that came with sql-ledger and it starts up fine. When I try to access
> admin.pl I can only get a screen requesting a password. Nothing I have
> tried works. I don't know if this is a config problem in sql, dbd-pg or
> where. Can anyone help? Thank you.

Re: Invoice number

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

You could use sequence too.

I increment the number in the code so I can create different combinations
to form a string for the invoice number.


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 Mon, 5 Nov 2001, Qaexl wrote:

> Hey there,
> 
> I'm in the middle of creating a couple modules for this client. One
> of them is a Point-of-Sales module that's a mishmash of the ct.pl and
> is.pl modules. More like a "wizard" to make it easier for the POS
> staff.  (I'll upload it somewhere if anyone's interested, once I'm
> done).  Going through there, though, I noticed that the invoice number
> doesn't use a sequence, but rather a chunk of Perl code that
> determines the last known invoice number, then increments it from
> there.
> 
> While this client won't have more than one POS terminal any time soon,
> I am concerned about this if there ever were. The liklihood of two
> people creating duplicate invoice number is slim to none -- but, I'd
> like to hear the developer's opinion on this. It is my understanding
> that the COMMIT command insures that there's no possibility of this
> happening.  Wouldn't it be safer to use a sequence instead? 
> 
> 

Invoice number

[Qaexl <qa...@ne...>]

Hey there,

I'm in the middle of creating a couple modules for this client. One
of them is a Point-of-Sales module that's a mishmash of the ct.pl and
is.pl modules. More like a "wizard" to make it easier for the POS
staff.  (I'll upload it somewhere if anyone's interested, once I'm
done).  Going through there, though, I noticed that the invoice number
doesn't use a sequence, but rather a chunk of Perl code that
determines the last known invoice number, then increments it from
there.

While this client won't have more than one POS terminal any time soon,
I am concerned about this if there ever were. The liklihood of two
people creating duplicate invoice number is slim to none -- but, I'd
like to hear the developer's opinion on this. It is my understanding
that the COMMIT command insures that there's no possibility of this
happening.  Wouldn't it be safer to use a sequence instead? 

-- 
-Qaexl-

unable to access sql-ledger

[cjs <cj...@pa...>]

I am running sus 7.1. I installed all the requisite packages for sql,
dbi, etc...
All went well. I installed sql-ledger, no problem. I am using the server
that came with sql-ledger and it starts up fine. When I try to access
admin.pl I can only get a screen requesting a password. Nothing I have
tried works. I don't know if this is a config problem in sql, dbd-pg or
where. Can anyone help? Thank you.

Re: no change capabilty for a transaction

[<ke...@dk...>]

On Sun, Nov 04, 2001 at 12:35:49PM -0700, Dieter Simader wrote:
> Hi all,
> 
> I mentioned to Keld already that SL has the options available to close the
> books. Here is how you do that.
> 
> CREATE RULE acc_trans_delete AS ON DELETE TO acc_trans WHERE old.transdate
> <= 'date' DO INSTEAD NOTHING;
> CREATE RULE acc_trans_input AS ON INSERT TO acc_trans WHERE
> new.transdate <= 'date' DO INSTEAD NOTHING;
> 
> This will close the books up to the date you specify!

Good! Could it be built into SL? Normally the
accountant would not have access to run psql raw, so it would
be nice if it could be done from one of the SL screens.

Kind regards
keld

RE: no change capabilty for a transaction

[Morten J. <mo...@ne...>]

VG9kZCBCb3lsZSBhbmQgSSBoYXZlIGJlZW4gZGlzY3Vzc2luZyB0aGlzIHRvcGljIGZvciB5ZWFy
cy4gSGVyZSBpcyBhbg0KZXh0cmFjdCBmcm9tIGFuIGludGVybmFsIGRvY3VtZW50LCB3cml0dGVu
IGJ5IG15c2VsZi4gDQogDQoiREVBIGltcG9ydGFuY2UgZGVyaXZlcyBmcm9tIHRoZSBub3Rpb24g
dGhhdCB3aGF0IGlzIHdyaXR0ZW4gZG93biBpcw0Kc2lnbmlmaWNhbnQgb3IgZXZlbiB0cnVlLiBU
aGUgZXZlcnlkYXkgZXZpZGVuY2Ugb2YgdGhpcyBpcyB0aGUNCmltcG9ydGFuY2Ugb2Ygbm90ZXMg
aW4ganVyaWRpY2FsIGNhc2VzLiINCiANCi4uLmFuZC4uLg0KIA0KDQoiRHVyaW5nIGFsbCB0aGUg
cHJvY2Vzc2VzIHdoaWNoIG1vZGlmeSBkYXRhLCBpdCBpcywgYXQgbGVhc3QgZm9yIEdMLA0KcmVx
dWlyZWQgdG8gb2J0YWluIGFuIGF1ZGl0IHRyYWlsLiAgQW4gYXVkaXQgdHJhaWwgaXMgYSBsb2cg
b3IgZG9jdW1lbnQNCm9mIGFsbCBjaGFuZ2VzIHRvIGEgbGVkZ2VyLiBUaGUgcHJpbmNpcGxlIGF1
ZGl0IHRyYWlsIGlzIHRoZSBsZWRnZXINCml0c2VsZiwgY29uc2lzdGluZyBvZiBhIGhpc3Rvcnkg
b2YgcmVhbCBlbnRyaWVzLiAgQSBmdXJ0aGVyIGF1ZGl0IHRyYWlsDQpyZXBvcnRpbmcgZGVsZXRp
b25zIGZyb20gYSBsZWRnZXIsIGlkZW50aXRpZXMgb2Ygb3BlcmF0b3JzIGV0Yy4gaXMNCnJlcXVp
cmVkIHdoZW4gZW50cmllcyBhcmUgbWFkZSBieSBwYXJ0aWVzIG90aGVyIHRoYW4gdGhlIG93bmVy
KHMpLCBhbmQNCmluIHNvbWUgY291bnRyaWVzIGV2ZW4gaW4gY2FzZXMgb2YgaW5kaXZpZHVhbHPi
gJkgcmVjb3Jkcy4gIA0KDQogDQoNClRoaXMgaXMgcXVpdGUgaW4gY29uZmxpY3Qgb2YgdGhlIFNN
RSBwcmFjdGljZSB3aXRoIFF1aWNrYm9vayBpbiBVUywgYW5kDQpUb2RkIEJveWxlIHZvaWNlcyBp
biB0aGUgZm9sbG93aW5nIHdheTog4oCcSW4gb3RoZXIgd29yZHMsIGluZGl2aWR1YWxzIGFyZQ0K
cmVxdWlyZWQgdG8gdXNlIHNvZnR3YXJlIHdoaWNoIGtlZXBzIHRyYWNrIG9mIHRoZSBvd25lcnPi
gJkgb3duIGRlbGV0aW9ucywNCnRvIHByb3ZpZGUgZXZpZGVuY2UgYWdhaW5zdCBoaW1zZWxmLiAg
SXNu4oCZdCB0aGF0IHJpZGljdWxvdXM/ICBBbmQNCnNvZnR3YXJlIGRldmVsb3BlcnMsIGxpa2Ug
YWNjb3VudGFudHMsIGFyZSBhbGlnbmVkIGFnYWluc3QgdGhlIGludGVyZXN0cw0Kb2YgdGhlaXIg
b3duIGNsaWVudHMsIGluIGVmZmVjdCBhc2tpbmcgZm9yIG1vbmV5IGZvciB0aGlzIHNlcnZpY2Uu
4oCdDQoNCldoYXQncyByZWFsbHkgaW4gc3Rha2UgaGVyZSwgaXMgdGhlIGNvbmZpZGVuY2Ugb2Yg
YWNjb3VudGluZywgd2hpY2ggaXMNCmJhc2VkIG9uIHRoZSBub3Rpb24gb2YgdGhhdCB3aGF0IGlz
IHdyaXR0ZW4gZG93biBpcyB0cnVlIChhdCBsYXN0IGFzIGZhcg0KYXMgeW91IHNlZSBpdCBhdCB0
aGUgcG9pbnQgb2YgcmVnaXN0ZXJpbmcpLiBJIHRoZSBib29ra2VlcGVyIGxhdGVyDQpjaGFuZ2Ug
aGlzIG1pbmQsIGhlIG11c3QgZXhwbGljaXQgcmVjb3JkIHRoZSBjaGFuZ2VzIGFuZCByZWZlciB0
byB0aGUNCmVhcmxpZXIgdHJ1dGguDQoNCiANCg0KVGhpcyBpcyBiYXNlZCBvbiBmaXZlIGh1bmRy
ZWQgeWVhcnMgb2YgcHJhY3RpY2U7IFBhY2lvbGkgKDE0OTMpIGRvIHN0YXRlDQppdCB0aGlzIHdh
eTogInN0YXJ0IGVhY2ggdHJhbnNhY3Rpb24gd2l0aCBhIGNyb3NzLCBhbmQgZG8gaXQgaW4gdGhl
IG5hbWUNCm9mIFRoZSBGYXRoZXIsIFRoZSBTb24gYW5kIFRoZSBIb2x5IFNwaXJpdCwgYW5kIHRo
ZW4gd3JpdGUgdGhlDQp0cmFuc2FjdGlvbiBkb3duLiBUaGVuIHRoZSB3cml0dGVuIHRyYW5zYWN0
aW9uIHdpbGwgcmVwcmVzZW50IHRoZQ0KdHJ1dGguIiAoZnJlZWx5IHRyYW5zbGF0ZWQgYnkgZWRp
dG9yKS4NCg0KIA0KDQpTbyBJIHdvdWxkIHJhdGhlciBzYXksIHRoYXQgU01FcyBpcyBoYXJ2ZXN0
aW5nIHRoZSBmcnVpdHMgb2YgdGhpcw0KdHJhZGl0aW9uLiBXaGVuIHRoZXkgZG8gdGhlaXIgYWNj
b3VudHMgYWNjb3JkaW5nIHRvIHRoZSBwcmFjdGljZSB0aGV5DQphcmUgYmVsaWV2ZWQgYnkgdGhl
IGdvdmVybm1lbnQsIGN1c3RvbWVycywgcHJvdmlkZXJzIGFuZCBiYW5rcyAoc29tZQ0KdGltZXMg
YXQgbGVhc3QgOi0pIg0KDQogDQoNCkkgd291bGQganVzdCBhZGQsIHRoYXQgdGhlIE5vcndlZ2lh
biBhdXRob3JpdGllcyBpbiAxOTkzIGFjY2VwdGVkDQpOZXRhY2NvdW50cyAoRWNvbm9taWNhIGFz
KSBzb2x1dGlvbiwgd2hpY2ggd2FzIHRvIGVuYWJsZQ0KcGFzc3dvcmRwcm90ZWN0aW5nIG9mIGNs
b3NlZCBwZXJpb2RzLiBBbmQgdGhhdCB0aGUgcmVwb3J0cyBleHBsaWNpdGx5DQpzdGF0ZWQgaWYg
dGhlIHJlcG9ydCByZWZsZWN0ZWQgY2xvc2VkIHBlcmlvZHMuDQoNCiANCg0KWW91IHByb2JhYmx5
IGFsc28gd291bGQgbGlrZSB0byBrbm93IHRoYXQgd3d3Lm5ldGFjY291bnQuY29tIGRvZXMgb2Zm
ZXINCmF1dG9tYXRpYyByZXZlcnNpbmcgb2YgdHJhbnNhY3Rpb25zLCB3aXRoIHJlcG9ydHMgdGhh
dCBpbmNsdWRlIHRoZQ0KcmV2ZXJzZWQgdHJhbnNhY3Rpb25zLg0KDQogDQoNCllvdSB3b3VsZCBh
bHNvIHByb2JhYmx5IGZpbmQgYSBsb3Qgb2YgaW50ZXJlc3RpbmcgZGV0YWlscyBpbiBUb2RkJ3MN
CmFydGljbGUgZnJvbSB0aGUgc2FtZSBwZXJpb2QgYXQgIGh0dHA6Ly93d3cuYXJhcHhtbC5uZXQv
TkRFQWRlZi5odG0NCjxodHRwOi8vd3d3LmFyYXB4bWwubmV0Lz4gDQoNCiANCg0KTW9ydGVuIEph
Y29ic2VuDQoNClZpY2UgUHJlc2lkZW50IG9mIE5leHQgR2VuZXJhdGlvbiBTZXJ2aWNlcw0KDQpO
ZXRhY2NvdW50IGFzLCBOb3J3YXkNCg0KIA0KDQoJLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0g
DQoJRnJvbTogS2VsZCBKw7hybiBTaW1vbnNlbiANCglTZW50OiBsw7ggMDMuMTEuMjAwMSAxODoy
MCANCglUbzogDQoJQ2M6IHNxbC1sZWRnZXItdXNlcnNAbGlzdHMuc291cmNlZm9yZ2UubmV0IA0K
CVN1YmplY3Q6IG5vIGNoYW5nZSBjYXBhYmlsdHkgZm9yIGEgdHJhbnNhY3Rpb24NCgkNCgkNCg0K
CUhpICENCgkNCglJIHRhbGtlZCB3aXRoIERpZXRlciBhYm91dCBhIG5lZWQgZm9yIG5vdCBiZWlu
Zw0KCWFibGUgdG8gY2hhbmdlIGEgdHJhbnNhY3Rpb24sIG9uY2UgaXQgaGFzIGJlZW4gZW50ZXJl
ZC4NCglUaGlzIGlzIGEgcmVxdWlyZW1lbnQgYnkgRGFuaXNoIGxhdywgc28gaXQgaXMgaW1wb3J0
YW50DQoJZm9yIERhbmVzIHNxbC1sZWRnZXIgdXNlcnMgdG8gaGF2ZSB0aGF0IGNhcGFiaWxpdHku
DQoJDQoJSSB3b25kZXIgaWYgdGhpcyBpcyBhIHJlcXVpcmVtZW50IG9uIG90aGVyIGNvdW50cmll
cy4NCglEb2VzIGFueW9uZSBvdXQgdGhlcmUgaGF2ZSBpbmZvcm1hdGlvbiBvbiB0aGlzPw0KCQ0K
CUtpbmQgcmVnYXJkcw0KCUtlbGQgU2ltb25zZW4NCgkNCgkNCg0K

Re: no change capabilty for a transaction

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

Hi all,

I mentioned to Keld already that SL has the options available to close th=
e
books. Here is how you do that.

CREATE RULE acc_trans_delete AS ON DELETE TO acc_trans WHERE old.transdat=
e
<=3D 'date' DO INSTEAD NOTHING;
CREATE RULE acc_trans_input AS ON INSERT TO acc_trans WHERE
new.transdate <=3D 'date' DO INSTEAD NOTHING;

This will close the books up to the date you specify!


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 Sun, 4 Nov 2001, Keld J=F8rn Simonsen wrote:

> On Sun, Nov 04, 2001 at 12:17:25AM -0500, Herb Richter wrote:
> >=20
> > On Sat, 3 Nov 2001, Keld J=F8rn Simonsen wrote:
> >=20
> > > Hi !
> > >
> > > I talked with Dieter about a need for not being
> > > able to change a transaction, once it has been entered.
> > > This is a requirement by Danish law, so it is important
> > > for Danes sql-ledger users to have that capability.
> >=20
> > 	Do you mean that once *any* transaction is entered it cannot be
> > changed?  even if it just needs to be corrected?
>=20
> I think there should be two options:
> 1. to "close" the books once in a while, that is, mark all
> transactions up to a given time as unchangeable. Could be done as
> a global variable per database, that is tested before any
> change of a transaction.
>=20
> 2. To "close" every transaction every time a new one is entered.
> This could also be a global variable per database.
>=20
> I am not sure whether the granularity is good enough.
> Should one be able to close only parts of a database?
> Eg if there were department dependent bookkeeping, then
> only for a certain department.
>=20
> In all cases it should not require administrative privileges,
> but should be available per database, and to the one that does the
> bookkeeping. The privilege should probably be available to people that
> are allowed to change the setup for a database, and available on the
> preferences menu.
>=20
> Kind regards
> Keld
>=20
>=20

Re: no change capabilty for a transaction

[<ke...@dk...>]

On Sun, Nov 04, 2001 at 12:17:25AM -0500, Herb Richter wrote:
> 
> On Sat, 3 Nov 2001, Keld Jørn Simonsen wrote:
> 
> > Hi !
> >
> > I talked with Dieter about a need for not being
> > able to change a transaction, once it has been entered.
> > This is a requirement by Danish law, so it is important
> > for Danes sql-ledger users to have that capability.
> 
> 	Do you mean that once *any* transaction is entered it cannot be
> changed?  even if it just needs to be corrected?

I think there should be two options:
1. to "close" the books once in a while, that is, mark all
transactions up to a given time as unchangeable. Could be done as
a global variable per database, that is tested before any
change of a transaction.

2. To "close" every transaction every time a new one is entered.
This could also be a global variable per database.

I am not sure whether the granularity is good enough.
Should one be able to close only parts of a database?
Eg if there were department dependent bookkeeping, then
only for a certain department.

In all cases it should not require administrative privileges,
but should be available per database, and to the one that does the
bookkeeping. The privilege should probably be available to people that
are allowed to change the setup for a database, and available on the
preferences menu.

Kind regards
Keld

Re: no change capabilty for a transaction

[Herb R. <he...@bu...>]

On Sat, 3 Nov 2001, Keld J=F8rn Simonsen wrote:

> Hi !
>
> I talked with Dieter about a need for not being
> able to change a transaction, once it has been entered.
> This is a requirement by Danish law, so it is important
> for Danes sql-ledger users to have that capability.

	Do you mean that once *any* transaction is entered it cannot be
changed?  even if it just needs to be corrected?

> I wonder if this is a requirement on other countries.
> Does anyone out there have information on this?
>
> Kind regards
> Keld Simonsen
>

--=20
Herb Richter,
Toronto, Ontario
http://www.partsandservice.com

Re: no change capabilty for a transaction

[Herb R. <he...@bu...>]

On Sat, 3 Nov 2001, Keld J=F8rn Simonsen wrote:

> Hi !
>
> I talked with Dieter about a need for not being
> able to change a transaction, once it has been entered.
> This is a requirement by Danish law, so it is important
> for Danes sql-ledger users to have that capability.
>
> I wonder if this is a requirement on other countries.
> Does anyone out there have information on this?
>
> Kind regards
> Keld Simonsen
>

	I too have talked to Dieter about something like this; ie to be
able to "close the books" at some point in time as after the fiscal year
end.
	My interest is actually to contribute to sql-ledger by adding
this function (along with some multi-currency function) but being new
to SL, this list and to SL's coding style I thought it better to start
with something easy like a phonebook (and now contact "manager").

	AW, my initial look at SL's structure suggests to me that closing
out a period could be done by providing an input for a "closed-as-at" dat=
e
that then is checked before any transactions are edited, deleted or added.
This closing date would require admin or superuser privileges.  If monthl=
y
closings are necessary then that would work also.  In my mind this would
preserve SL's fluid approach to accounting periods (which I like a lot)
while still giving some comfort to the auditors and protecting against
routine errors that could affect entries that are reconciled and
considered final.

	If some extraordinary situation arose where a closed period's
transactions do need to be changed, the admin / superuser could roll back
the closed-as-at date.  I doubt if there is any prohibition to reopening =
a
closed set of books in Canada's Income Tax Act, but I'm sure Revenue
Canada (now Canada Customs and Revenue ...) would take a very long look a=
t
a companies activities if this was done without a *very* good reason and
without refilling amended statements and tax returns.


--=20

Herb Richter,
Toronto, Ontario
http://www.partsandservice.com

Re: no change capabilty for a transaction

[Terry C. <te...@wo...>]

"Leo R. Masciuch" wrote:
> 
> I don't believe that GAAP (Generally Accepted Accounting Principles)
> requires the inability to alter or delete transactions. 

As I understand it, you do not alter a transaction, but reverse the
transaction. So if I make a pay a bill and accidentally record it as
being done by my cheque account, rather than my credit card, that
accidental transaction is reversed (net effect zero), rather than
deleted. This entry and reversal simply records the mistake, so should
it have caused some other problems, you/someone can find the cause in
the future.

-- 
   Terry Collins {:-)}}} Ph(02) 4627 2186 Fax(02) 4628 7861  
   email: te...@wo...  www: http://www.woa.com.au  
   Wombat Outdoor Adventures <Bicycles, Books, Computers, GIS>

 "People without trees are like fish without clean water"

RE: no change capabilty for a transaction

[Leo R. M. <Le...@Ne...>]

I don't believe that GAAP (Generally Accepted Accounting Principles)
requires the inability to alter or delete transactions.  This is still a
big argument because the proponents of the inability want to assume that
everyone's dishonest.  On the other hand, I had a client who stopped
doing his bookkeeping because he couldn't figure out how the reverse an
entry in the GL.  While some accounting professionals might want to
demand that we make the bookkeeping sufficiently difficult that most
small businesses would have to have their accountant do the work, the
ultimate principle of GAAP is that you get the right answer in a timely
manner.=20

Most countries only refer to GAAP by reference.  I suspect that Denmark
doesn't specifically prohibit the removal and editing of transactions
but someone has interpreted GAAP to include audit trail and therefore is
saying that the law says so.  I had a client here in Canada who had been
told the same thing here and, when challenged, had to admit that it was
only his interpretation of GAAP and no such Canadian law existed
verbatim. What got that accountant's services terminated was that he
wasn't aware of the regulations that could have saved our mutual client
much money. =20

As we teach people new to the net, corroborate your information with at
least two other independent sources.  Don't take my word for it, see if
you can get a reference to the legislation and look it up.

Regards,
Leo R Masciuch, MBA, PEng
Netryst Corp.
5051 Vantage Cres NW
Calgary, AB  T3A 1X6  CANADA
Le...@Ne...


-----Original Message-----
From: root [mailto:ro...@ma...]
Sent: November 3, 2001 12:36
To: ke...@dk...; nj...@ci...
Cc: sql...@li...
Subject: Re: no change capabilty for a transaction


Quickbooks (uughhh) has such a feature and here's how it works:
once you close out your year, you can view all transactions but not edit
prior year transactions.
Transactions can be edited, but only by the "master user" i.e. the
sysadmin.

But, for the pureist accountants out there, i do agree that no
transaction should ever be editable once entered, if you goof you just
do a GL transfer and add a comment - ' - $xxx.xx to correct transaction
12345.

but, just my two cents!

Re: no change capabilty for a transaction

[<pe...@my...>]

On Sat, Nov 03, 2001 at 06:20:57PM +0100, Keld J?rn Simonsen wrote:
> Hi !
> 
> I talked with Dieter about a need for not being
> able to change a transaction, once it has been entered. 
> This is a requirement by Danish law, so it is important
> for Danes sql-ledger users to have that capability.
> 
> I wonder if this is a requirement on other countries.
> Does anyone out there have information on this?

I work in a medical field were we have the same issues with
electronic medical records. This is solved my making a nightly backup
onto non rewritable media, ie cd. This has the advantage of providing a
backup and a continus record at the same time.
Just my 2c
peter

Re: no change capabilty for a transaction

[Paulo R. <pro...@vi...>]

Keld J=F8rn Simonsen wrote:
>=20
> Hi !
>=20
> I talked with Dieter about a need for not being
> able to change a transaction, once it has been entered.
> This is a requirement by Danish law, so it is important
> for Danes sql-ledger users to have that capability.
>=20
> I wonder if this is a requirement on other countries.
> Does anyone out there have information on this?
>=20
> Kind regards
> Keld Simonsen

Hi,

in practice thats impossible; any DBA can hack the database when there
are system errors. The "proper" way would of course be entering a
cancelling transaction, but sometimes that's not possible.=20
But I agree, normal users shouldn't be allowed to edit "posted"
transactions - if you intend to use the accounting information for
official purposes. That's certainly the case with portuguese law.

Cheers,
Paulo Rodrigues

Re: no change capabilty for a transaction

[root <ro...@ma...>]

Quickbooks (uughhh) has such a feature and here's how it works:
once you close out your year, you can view all transactions but not edit prior year transactions.
Transactions can be edited, but only by the "master user" i.e. the sysadmin.

But, for the pureist accountants out there, i do agree that no transaction should ever be editable once entered, if you goof you just do a GL transfer and add a comment - ' - $xxx.xx to correct transaction 12345.

but, just my two cents!