From: <In...@wi...> - 2004-10-11 17:28:08
|
Hello Kent, >Sent: Monday, October 11, 2004 5:59 PM >To: sql...@sq... > >My theory was a plugin to SL. Working with SL, but not within. My fear >would be to create a module, then the next update that I wanted came >out, I'd have to recode the payroll. I think a good upgrade friendly way is to use your own frontend and backend code (maybe including all helper modules like io.pl, Form.pm..., too) Then it will be usefull to create an own tableset and not change the sql-ledger tables. >I'm not a coder, but I do dabble. I'm sure that I will be using >improper jargon, but here's what I've came up with at this point: > >My module would be perl/sql based. It would work hand in hand with SL, >posting approiatly directly to the SL db. I wouldn't post data directly into the SL db, because of future changes and dependencies to other tables. Posting data directly into the sql-ledger tables is in my eyes to chancy, just one systematic error in your data entrys which will appear after thousands of bookings... A better way may the use of the gl.pl of sql-ledger. Just simulate a booking in gl and analyze the posted data. This way you create easily your own link and post it to the gl.pl. If the gl-api will change its a small job to adjust your link. For the rest I cant say anything more, I don't need payroll. I found this in an old (2002-12) users posting , maybe it helps: http://cbbrowne.com/downloads/sql-payroll.tgz (Complete posting http://www.freelists.org/archives/sql-ledger-users/12-2002/msg00126.html) Good luck Udo Spallek |