sql-ledger-users — SQL-Ledger users

[SL] How to add a RIF/NIT in invoice

[Danilo M. <dan...@ca...>]

In the add client page, i can put a RIF/NIT Value,

How can i add this value to the invoice editing the templates?

Thanks

[SL] PR, SQL-Ledger in the news

[C. D. H. <Du...@Du...>]

Perhaps not the best PR, but still getting the name out there is always 
good:  http://yro.slashdot.org/article.pl?sid=07/04/15/1759254

Dunc

[SL] problem after upgrade from 2.6.27 to 2.8.1

[Andrei K. <and...@ma...>]

After upgrade from command line with setup.pl from 2.6.27 to 2.8.1 I can't 
change user access preferences anymore. If I select General Ledger or Goods & 
Services for particular user and save configuration it still can't access 
those menus. Same problem with any other checkbox in configuration. I even 
tried to make other access template- it saves template name but access rules 
stays as default- configuration changes is not stored. Tried adding new 
users- same result.

Wassup?

Re: [SL] 2.8.1 bugs

[Andrei K. <and...@ma...>]

I upgraded from command line as root user but:
-----------------------------------------------------------------------------------
Downloading sql-ledger-2.8.1.tar.gz ....
U.K .... failed!
New York, U.S.A ....
Looking up voxel.dl.sourceforge.net
Making HTTP connection to voxel.dl.sourceforge.net
Alert!: Unable to connect to remote host.

lynx: Can't access startfile 
http://voxel.dl.sourceforge.net/sourceforge/sql-ledger/sql-ledger-2.8.1.tar.gz
failed!
Arizona, U.S.A .... failed!
California, U.S.A .... ok!
Decompressing sql-ledger-2.8.1.tar.gz ... done
Unpacking sql-ledger-2.8.1.tar ... done
cleaning up ... done
/usr/local/etc/apache22/extra/httpd-dav.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-default.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-info.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-languages.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-manual.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-mpm.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-multilang-errordoc.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-ssl.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-userdir.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-vhosts.conf: Permission denied
/usr/local/etc/apache22/httpd.conf: Permission denied

This is a new installation.


Webserver directives were written to

  /usr/local/etc/apache22/extra/sql-ledger-httpd.conf
/usr/local/etc/apache22/extra/httpd-dav.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-default.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-info.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-languages.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-manual.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-mpm.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-multilang-errordoc.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-ssl.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-userdir.conf: Permission denied
/usr/local/etc/apache22/extra/httpd-vhosts.conf: Permission denied
/usr/local/etc/apache22/httpd.conf: Permission denied
-----------------------------------------------------------------------------------

Where is information about what I have to upgrade in these files?

[SL] Licensing

[Dr E. W. L. <el...@li...>]

Are there plans to change the licensing for SQL-Ledger?

el

[SL] customernumber in AR aging report

[Wan L. <big...@ya...>]

i would like to display the customernumber field in my AR Aging report. does
anyone know how this is done? i tried adding <%customernumber%> to
statement.tex, but it did not work.

wan ling





      
____________________________________________________ 
Yahoo! Singapore Answers 
Real people. Real questions. Real answers. Share what you know at http://answers.yahoo.com.sg

Re: [SL] migrating to a new machine

[Paul T. <pt...@wa...>]

RYAN M. vAN GINNEKEN wrote:
> Sorry for the ridiculously long post but i have dont have much experience with databases in 
This from a Computer King company that provides Web Services and 
automated backup gives me no hard sales pitch to say the least. Why run 
on Windows and Pg_Admin and not with Linux and the usual psql < part? 
Did you run the shebang thing at all?

Greetz,
Paul

Re: [SL] migrating to a new machine

[RYAN M. v. G. <lu...@co...>]

Sorry for the ridiculously long post but i have dont have much experience with databases in fact i used a gui to do the dump and restore seemed much easier.  Here is a list of the outputs there are several errors and when i add stuff to sql-ledger it does not save anything.
  Allows me to enter data just forgets everything.

D:\Program Files\pgAdmin III\1.6\pg_dump.exe -i -h computerking.ca -p 5432 -U pgsql -F c -b -o -v -f "D:\Documents and Settings\King\king.backup" computerking
pg_dump: reading schemas
pg_dump: reading user-defined functions
pg_dump: reading user-defined types
pg_dump: reading procedural languages
pg_dump: reading user-defined aggregate functions
pg_dump: reading user-defined operators
pg_dump: reading user-defined operator classes
pg_dump: reading user-defined operator families
pg_dump: reading user-defined conversions
pg_dump: reading user-defined tables
pg_dump: reading table inheritance information
pg_dump: reading rewrite rules
pg_dump: reading type casts
pg_dump: finding inheritance relationships
pg_dump: reading column info for interesting tables
pg_dump: finding the columns and types of table "makemodel"
pg_dump: finding the columns and types of table "gl"
pg_dump: finding default expressions of table "gl"
pg_dump: finding the columns and types of table "chart"
pg_dump: finding default expressions of table "chart"
pg_dump: finding the columns and types of table "gifi"
pg_dump: finding the columns and types of table "defaults"
pg_dump: finding default expressions of table "defaults"
pg_dump: finding the columns and types of table "acc_trans"
pg_dump: finding default expressions of table "acc_trans"
pg_dump: finding the columns and types of table "invoice"
pg_dump: finding default expressions of table "invoice"
pg_dump: finding the columns and types of table "customer"
pg_dump: finding default expressions of table "customer"
pg_dump: finding the columns and types of table "parts"
pg_dump: finding default expressions of table "parts"
pg_dump: finding the columns and types of table "assembly"
pg_dump: finding the columns and types of table "ar"
pg_dump: finding default expressions of table "ar"
pg_dump: finding the columns and types of table "ap"
pg_dump: finding default expressions of table "ap"
pg_dump: finding the columns and types of table "partstax"
pg_dump: finding the columns and types of table "tax"
pg_dump: finding the columns and types of table "customertax"
pg_dump: finding the columns and types of table "vendortax"
pg_dump: finding the columns and types of table "oe"
pg_dump: finding default expressions of table "oe"
pg_dump: finding the columns and types of table "orderitems"
pg_dump: finding default expressions of table "orderitems"
pg_dump: finding the columns and types of table "exchangerate"
pg_dump: finding the columns and types of table "employee"
pg_dump: finding default expressions of table "employee"
pg_dump: finding the columns and types of table "shipto"
pg_dump: finding the columns and types of table "vendor"
pg_dump: finding default expressions of table "vendor"
pg_dump: finding the columns and types of table "project"
pg_dump: finding default expressions of table "project"
pg_dump: finding the columns and types of table "partsgroup"
pg_dump: finding default expressions of table "partsgroup"
pg_dump: finding the columns and types of table "status"
pg_dump: finding default expressions of table "status"
pg_dump: finding the columns and types of table "department"
pg_dump: finding default expressions of table "department"
pg_dump: finding the columns and types of table "dpt_trans"
pg_dump: finding the columns and types of table "business"
pg_dump: finding default expressions of table "business"
pg_dump: finding the columns and types of table "sic"
pg_dump: finding the columns and types of table "warehouse"
pg_dump: finding default expressions of table "warehouse"
pg_dump: finding the columns and types of table "inventory"
pg_dump: finding the columns and types of table "yearend"
pg_dump: finding the columns and types of table "partsvendor"
pg_dump: finding the columns and types of table "pricegroup"
pg_dump: finding default expressions of table "pricegroup"
pg_dump: finding the columns and types of table "partscustomer"
pg_dump: finding the columns and types of table "language"
pg_dump: finding the columns and types of table "audittrail"
pg_dump: finding default expressions of table "audittrail"
pg_dump: finding the columns and types of table "translation"
pg_dump: finding the columns and types of table "recurring"
pg_dump: finding default expressions of table "recurring"
pg_dump: finding the columns and types of table "recurringemail"
pg_dump: finding the columns and types of table "recurringprint"
pg_dump: finding the columns and types of table "jcitems"
pg_dump: finding default expressions of table "jcitems"
pg_dump: flagging inherited columns in subtables
pg_dump: reading indexes
pg_dump: reading indexes for table "makemodel"
pg_dump: reading indexes for table "gl"
pg_dump: reading indexes for table "chart"
pg_dump: reading indexes for table "gifi"
pg_dump: reading indexes for table "acc_trans"
pg_dump: reading indexes for table "invoice"
pg_dump: reading indexes for table "customer"
pg_dump: reading indexes for table "parts"
pg_dump: reading indexes for table "assembly"
pg_dump: reading indexes for table "ar"
pg_dump: reading indexes for table "ap"
pg_dump: reading indexes for table "partstax"
pg_dump: reading indexes for table "customertax"
pg_dump: reading indexes for table "vendortax"
pg_dump: reading indexes for table "oe"
pg_dump: reading indexes for table "orderitems"
pg_dump: reading indexes for table "exchangerate"
pg_dump: reading indexes for table "employee"
pg_dump: reading indexes for table "shipto"
pg_dump: reading indexes for table "vendor"
pg_dump: reading indexes for table "project"
pg_dump: reading indexes for table "partsgroup"
pg_dump: reading indexes for table "status"
pg_dump: reading indexes for table "department"
pg_dump: reading indexes for table "partsvendor"
pg_dump: reading indexes for table "pricegroup"
pg_dump: reading indexes for table "language"
pg_dump: reading indexes for table "audittrail"
pg_dump: reading indexes for table "translation"
pg_dump: reading indexes for table "jcitems"
pg_dump: reading constraints
pg_dump: reading foreign key constraints for table "gl"
pg_dump: reading foreign key constraints for table "customer"
pg_dump: reading foreign key constraints for table "ar"
pg_dump: reading foreign key constraints for table "ap"
pg_dump: reading foreign key constraints for table "oe"
pg_dump: reading foreign key constraints for table "vendor"
pg_dump: reading triggers
pg_dump: reading triggers for table "gl"
pg_dump: reading triggers for table "customer"
pg_dump: reading triggers for table "ar"
pg_dump: reading triggers for table "ap"
pg_dump: reading triggers for table "oe"
pg_dump: reading triggers for table "vendor"
pg_dump: reading dependency data
pg_dump: saving encoding = SQL_ASCII
pg_dump: saving standard_conforming_strings = off
pg_dump: saving database definition
pg_dump: dumping contents of table acc_trans
pg_dump: dumping contents of table ap
pg_dump: dumping contents of table ar
pg_dump: dumping contents of table assembly
pg_dump: dumping contents of table audittrail
pg_dump: dumping contents of table business
pg_dump: dumping contents of table chart
pg_dump: dumping contents of table customer
pg_dump: dumping contents of table customertax
pg_dump: dumping contents of table defaults
pg_dump: dumping contents of table department
pg_dump: dumping contents of table dpt_trans
pg_dump: dumping contents of table employee
pg_dump: dumping contents of table exchangerate
pg_dump: dumping contents of table gifi
pg_dump: dumping contents of table gl
pg_dump: dumping contents of table inventory
pg_dump: dumping contents of table invoice
pg_dump: dumping contents of table jcitems
pg_dump: dumping contents of table language
pg_dump: dumping contents of table makemodel
pg_dump: dumping contents of table oe
pg_dump: dumping contents of table orderitems
pg_dump: dumping contents of table parts
pg_dump: dumping contents of table partscustomer
pg_dump: dumping contents of table partsgroup
pg_dump: dumping contents of table partstax
pg_dump: dumping contents of table partsvendor
pg_dump: dumping contents of table pricegroup
pg_dump: dumping contents of table project
pg_dump: dumping contents of table recurring
pg_dump: dumping contents of table recurringemail
pg_dump: dumping contents of table recurringprint
pg_dump: dumping contents of table shipto
pg_dump: dumping contents of table sic
pg_dump: dumping contents of table status
pg_dump: dumping contents of table tax
pg_dump: dumping contents of table translation
pg_dump: dumping contents of table vendor
pg_dump: dumping contents of table vendortax
pg_dump: dumping contents of table warehouse
pg_dump: dumping contents of table yearend

Process returned exit code 0.


D:\Program Files\pgAdmin III\1.6\pg_restore.exe -i -h 192.168.0.23 -p 5432 -U pgsql -d king1 -v "D:\Documents and Settings\King\king.backup"
pg_restore: connecting to database for restore
pg_restore: [archiver (db)] Error while INITIALIZING:
pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "standard_conforming_strings"
    Command was: SET standard_conforming_strings = off;
pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "escape_string_warning"
    Command was: SET escape_string_warning = off;
pg_restore: creating SCHEMA public
pg_restore: creating COMMENT SCHEMA public
pg_restore: creating FUNCTION plpgsql_call_handler()
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 9; 1255 18172 FUNCTION plpgsql_call_handler() rmvg
pg_restore: [archiver (db)] could not execute query: ERROR:  function "plpgsql_call_handler" already exists with same argument types
    Command was: CREATE FUNCTION plpgsql_call_handler() RETURNS language_handler
    AS '$libdir/plpgsql', 'plpgsql_call_handler'
    LANGUAG...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.plpgsql_call_handler() OWNER TO rmvg;
                                                     ^
    Command was: ALTER FUNCTION public.plpgsql_call_handler() OWNER TO rmvg;
pg_restore: creating PROCEDURAL LANGUAGE plpgsql
pg_restore: [archiver (db)] Error from TOC entry 322; 16402 18173 PROCEDURAL LANGUAGE plpgsql pgsql
pg_restore: [archiver (db)] could not execute query: ERROR:  language "plpgsql" already exists
    Command was: CREATE TRUSTED PROCEDURAL LANGUAGE plpgsql HANDLER plpgsql_call_handler;
pg_restore: creating FUNCTION avgcost(integer)
pg_restore: [archiver (db)] Error from TOC entry 18; 1255 22758 FUNCTION avgcost(integer) sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $_$
               ^
    Command was: CREATE FUNCTION avgcost(integer) RETURNS double precision
    AS $_$
DECLARE
v_cost float;
v_qty float;
v_parts_id alias for...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.avgcost(integer) OWNER TO "sql-ledger"...
                                               ^
    Command was: ALTER FUNCTION public.avgcost(integer) OWNER TO "sql-ledger";
pg_restore: creating FUNCTION check_department()
pg_restore: [archiver (db)] Error from TOC entry 16; 1255 22749 FUNCTION check_department() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION check_department() RETURNS "trigger"
    AS $$
declare
  dpt_id int;
begin
  if new.department_id = 0 then
 ...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.check_department() OWNER TO "sql-ledge...
                                                 ^
    Command was: ALTER FUNCTION public.check_department() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION check_inventory()
pg_restore: [archiver (db)] Error from TOC entry 15; 1255 22747 FUNCTION check_inventory() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION check_inventory() RETURNS "trigger"
    AS $$
declare
  itemid int;
  row_data inventory%rowtype;
begin
  if...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.check_inventory() OWNER TO "sql-ledger...
                                                ^
    Command was: ALTER FUNCTION public.check_inventory() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION del_customer()
pg_restore: [archiver (db)] Error from TOC entry 12; 1255 22739 FUNCTION del_customer() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION del_customer() RETURNS "trigger"
    AS $$
begin
  delete from shipto where trans_id = old.id;
  delete from...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.del_customer() OWNER TO "sql-ledger";
                                             ^
    Command was: ALTER FUNCTION public.del_customer() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION del_department()
pg_restore: [archiver (db)] Error from TOC entry 11; 1255 22734 FUNCTION del_department() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION del_department() RETURNS "trigger"
    AS $$
begin
  delete from dpt_trans where trans_id = old.id;
  return...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.del_department() OWNER TO "sql-ledger"...
                                               ^
    Command was: ALTER FUNCTION public.del_department() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION del_exchangerate()
pg_restore: [archiver (db)] Error from TOC entry 14; 1255 22743 FUNCTION del_exchangerate() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION del_exchangerate() RETURNS "trigger"
    AS $$
declare
  t_transdate date;
  t_curr char(3);
  t_id int;
  d...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.del_exchangerate() OWNER TO "sql-ledge...
                                                 ^
    Command was: ALTER FUNCTION public.del_exchangerate() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION del_recurring()
pg_restore: [archiver (db)] Error from TOC entry 17; 1255 22754 FUNCTION del_recurring() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION del_recurring() RETURNS "trigger"
    AS $$
BEGIN
  DELETE FROM recurring WHERE id = old.id;
  DELETE FROM r...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.del_recurring() OWNER TO "sql-ledger";
                                              ^
    Command was: ALTER FUNCTION public.del_recurring() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION del_vendor()
pg_restore: [archiver (db)] Error from TOC entry 13; 1255 22741 FUNCTION del_vendor() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION del_vendor() RETURNS "trigger"
    AS $$
begin
  delete from shipto where trans_id = old.id;
  delete from v...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.del_vendor() OWNER TO "sql-ledger";
                                           ^
    Command was: ALTER FUNCTION public.del_vendor() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION del_yearend()
pg_restore: [archiver (db)] Error from TOC entry 10; 1255 22732 FUNCTION del_yearend() sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $$
               ^
    Command was: CREATE FUNCTION del_yearend() RETURNS "trigger"
    AS $$
begin
  delete from yearend where trans_id = old.id;
  return NULL...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.del_yearend() OWNER TO "sql-ledger";
                                            ^
    Command was: ALTER FUNCTION public.del_yearend() OWNER TO "sql-ledger";
pg_restore: creating FUNCTION lastcost(integer)
pg_restore: [archiver (db)] Error from TOC entry 19; 1255 22759 FUNCTION lastcost(integer) sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "$"
LINE 2:     AS $_$
               ^
    Command was: CREATE FUNCTION lastcost(integer) RETURNS double precision
    AS $_$
DECLARE
v_cost float;
v_parts_id alias for $1;
BEGIN
 ...
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "OWNER"
LINE 1: ALTER FUNCTION public.lastcost(integer) OWNER TO "sql-ledger...
                                                ^
    Command was: ALTER FUNCTION public.lastcost(integer) OWNER TO "sql-ledger";
pg_restore: creating TABLE acc_trans
pg_restore: [archiver] Error from TOC entry 1213; 1259 22518 TABLE acc_trans sql-ledger
pg_restore: [archiver] could not set default_tablespace to "": ERROR:  unrecognized configuration parameter "default_tablespace"
pg_restore: [archiver] could not set default_with_oids: ERROR:  unrecognized configuration parameter "default_with_oids"
pg_restore: creating TABLE ap
pg_restore: creating TABLE ar
pg_restore: creating TABLE assembly
pg_restore: creating TABLE audittrail
pg_restore: creating TABLE business
pg_restore: creating TABLE chart
pg_restore: creating TABLE customer
pg_restore: creating TABLE customertax
pg_restore: creating TABLE defaults
pg_restore: creating TABLE department
pg_restore: creating TABLE dpt_trans
pg_restore: creating TABLE employee
pg_restore: creating TABLE exchangerate
pg_restore: creating TABLE gifi
pg_restore: creating TABLE gl
pg_restore: creating SEQUENCE id
pg_restore: executing SEQUENCE SET id
pg_restore: creating TABLE inventory
pg_restore: creating TABLE invoice
pg_restore: creating SEQUENCE invoiceid
pg_restore: executing SEQUENCE SET invoiceid
pg_restore: creating TABLE jcitems
pg_restore: creating SEQUENCE jcitemsid
pg_restore: executing SEQUENCE SET jcitemsid
pg_restore: creating TABLE language
pg_restore: creating TABLE makemodel
pg_restore: creating TABLE oe
pg_restore: creating TABLE orderitems
pg_restore: creating SEQUENCE orderitemsid
pg_restore: executing SEQUENCE SET orderitemsid
pg_restore: creating TABLE parts
pg_restore: creating TABLE partscustomer
pg_restore: creating TABLE partsgroup
pg_restore: creating TABLE partstax
pg_restore: creating TABLE partsvendor
pg_restore: creating TABLE pricegroup
pg_restore: creating TABLE project
pg_restore: creating TABLE recurring
pg_restore: creating TABLE recurringemail
pg_restore: creating TABLE recurringprint
pg_restore: creating TABLE shipto
pg_restore: creating TABLE sic
pg_restore: creating TABLE status
pg_restore: creating TABLE tax
pg_restore: creating TABLE translation
pg_restore: creating TABLE vendor
pg_restore: creating TABLE vendortax
pg_restore: creating TABLE warehouse
pg_restore: creating TABLE yearend
pg_restore: restoring data for table "acc_trans"
pg_restore: restoring data for table "ap"
pg_restore: restoring data for table "ar"
pg_restore: restoring data for table "assembly"
pg_restore: restoring data for table "audittrail"
pg_restore: restoring data for table "business"
pg_restore: restoring data for table "chart"
pg_restore: restoring data for table "customer"
pg_restore: restoring data for table "customertax"
pg_restore: restoring data for table "defaults"
pg_restore: restoring data for table "department"
pg_restore: restoring data for table "dpt_trans"
pg_restore: restoring data for table "employee"
pg_restore: restoring data for table "exchangerate"
pg_restore: restoring data for table "gifi"
pg_restore: restoring data for table "gl"
pg_restore: restoring data for table "inventory"
pg_restore: restoring data for table "invoice"
pg_restore: restoring data for table "jcitems"
pg_restore: restoring data for table "language"
pg_restore: restoring data for table "makemodel"
pg_restore: restoring data for table "oe"
pg_restore: restoring data for table "orderitems"
pg_restore: restoring data for table "parts"
pg_restore: restoring data for table "partscustomer"
pg_restore: restoring data for table "partsgroup"
pg_restore: restoring data for table "partstax"
pg_restore: restoring data for table "partsvendor"
pg_restore: restoring data for table "pricegroup"
pg_restore: restoring data for table "project"
pg_restore: restoring data for table "recurring"
pg_restore: restoring data for table "recurringemail"
pg_restore: restoring data for table "recurringprint"
pg_restore: restoring data for table "shipto"
pg_restore: restoring data for table "sic"
pg_restore: restoring data for table "status"
pg_restore: restoring data for table "tax"
pg_restore: restoring data for table "translation"
pg_restore: restoring data for table "vendor"
pg_restore: restoring data for table "vendortax"
pg_restore: restoring data for table "warehouse"
pg_restore: restoring data for table "yearend"
pg_restore: creating INDEX acc_trans_chart_id_key
pg_restore: creating INDEX acc_trans_source_key
pg_restore: creating INDEX acc_trans_trans_id_key
pg_restore: creating INDEX acc_trans_transdate_key
pg_restore: creating INDEX ap_employee_id_key
pg_restore: creating INDEX ap_id_key
pg_restore: creating INDEX ap_invnumber_key
pg_restore: creating INDEX ap_ordnumber_key
pg_restore: creating INDEX ap_quonumber_key
pg_restore: creating INDEX ap_transdate_key
pg_restore: creating INDEX ap_vendor_id_key
pg_restore: creating INDEX ar_customer_id_key
pg_restore: creating INDEX ar_employee_id_key
pg_restore: creating INDEX ar_id_key
pg_restore: creating INDEX ar_invnumber_key
pg_restore: creating INDEX ar_ordnumber_key
pg_restore: creating INDEX ar_quonumber_key
pg_restore: creating INDEX ar_transdate_key
pg_restore: creating INDEX assembly_id_key
pg_restore: creating INDEX audittrail_trans_id_key
pg_restore: creating INDEX chart_accno_key
pg_restore: creating INDEX chart_category_key
pg_restore: creating INDEX chart_gifi_accno_key
pg_restore: creating INDEX chart_id_key
pg_restore: creating INDEX chart_link_key
pg_restore: creating INDEX customer_contact_key
pg_restore: creating INDEX customer_customer_id_key
pg_restore: creating INDEX customer_customernumber_key
pg_restore: creating INDEX customer_id_key
pg_restore: creating INDEX customer_name_key
pg_restore: creating INDEX department_id_key
pg_restore: creating INDEX employee_id_key
pg_restore: creating INDEX employee_login_key
pg_restore: creating INDEX employee_name_key
pg_restore: creating INDEX exchangerate_ct_key
pg_restore: creating INDEX gifi_accno_key
pg_restore: creating INDEX gl_description_key
pg_restore: creating INDEX gl_employee_id_key
pg_restore: creating INDEX gl_id_key
pg_restore: creating INDEX gl_reference_key
pg_restore: creating INDEX gl_transdate_key
pg_restore: creating INDEX invoice_id_key
pg_restore: creating INDEX invoice_trans_id_key
pg_restore: creating INDEX jcitems_id_key
pg_restore: creating INDEX language_code_key
pg_restore: creating INDEX makemodel_make_key
pg_restore: creating INDEX makemodel_model_key
pg_restore: creating INDEX makemodel_parts_id_key
pg_restore: creating INDEX oe_employee_id_key
pg_restore: creating INDEX oe_id_key
pg_restore: creating INDEX oe_ordnumber_key
pg_restore: creating INDEX oe_transdate_key
pg_restore: creating INDEX orderitems_id_key
pg_restore: creating INDEX orderitems_trans_id_key
pg_restore: creating INDEX parts_description_key
pg_restore: creating INDEX parts_id_key
pg_restore: creating INDEX parts_partnumber_key
pg_restore: creating INDEX partsgroup_id_key
pg_restore: creating INDEX partsgroup_key
pg_restore: creating INDEX partstax_parts_id_key
pg_restore: creating INDEX partsvendor_parts_id_key
pg_restore: creating INDEX partsvendor_vendor_id_key
pg_restore: creating INDEX pricegroup_id_key
pg_restore: creating INDEX pricegroup_pricegroup_key
pg_restore: creating INDEX project_id_key
pg_restore: creating INDEX projectnumber_key
pg_restore: creating INDEX shipto_trans_id_key
pg_restore: creating INDEX status_trans_id_key
pg_restore: creating INDEX translation_trans_id_key
pg_restore: creating INDEX vendor_contact_key
pg_restore: creating INDEX vendor_id_key
pg_restore: creating INDEX vendor_name_key
pg_restore: creating INDEX vendor_vendornumber_key
pg_restore: creating INDEX vendortax_vendor_id_key
pg_restore: creating TRIGGER check_department
pg_restore: [archiver (db)] Error from TOC entry 1629; 16412 22750 TRIGGER check_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function check_department() does not exist
    Command was: CREATE TRIGGER check_department
    AFTER INSERT OR UPDATE ON ar
    FOR EACH ROW
    EXECUTE PROCEDURE check_department();
pg_restore: creating TRIGGER check_department
pg_restore: [archiver (db)] Error from TOC entry 1633; 16412 22751 TRIGGER check_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function check_department() does not exist
    Command was: CREATE TRIGGER check_department
    AFTER INSERT OR UPDATE ON ap
    FOR EACH ROW
    EXECUTE PROCEDURE check_department();
pg_restore: creating TRIGGER check_department
pg_restore: [archiver (db)] Error from TOC entry 1624; 16412 22752 TRIGGER check_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function check_department() does not exist
    Command was: CREATE TRIGGER check_department
    AFTER INSERT OR UPDATE ON gl
    FOR EACH ROW
    EXECUTE PROCEDURE check_department();
pg_restore: creating TRIGGER check_department
pg_restore: [archiver (db)] Error from TOC entry 1637; 16412 22753 TRIGGER check_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function check_department() does not exist
    Command was: CREATE TRIGGER check_department
    AFTER INSERT OR UPDATE ON oe
    FOR EACH ROW
    EXECUTE PROCEDURE check_department();
pg_restore: creating TRIGGER check_inventory
pg_restore: [archiver (db)] Error from TOC entry 1638; 16412 22748 TRIGGER check_inventory sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function check_inventory() does not exist
    Command was: CREATE TRIGGER check_inventory
    AFTER UPDATE ON oe
    FOR EACH ROW
    EXECUTE PROCEDURE check_inventory();
pg_restore: creating TRIGGER del_customer
pg_restore: [archiver (db)] Error from TOC entry 1628; 16412 22740 TRIGGER del_customer sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_customer() does not exist
    Command was: CREATE TRIGGER del_customer
    AFTER DELETE ON customer
    FOR EACH ROW
    EXECUTE PROCEDURE del_customer();
pg_restore: creating TRIGGER del_department
pg_restore: [archiver (db)] Error from TOC entry 1630; 16412 22735 TRIGGER del_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_department() does not exist
    Command was: CREATE TRIGGER del_department
    AFTER DELETE ON ar
    FOR EACH ROW
    EXECUTE PROCEDURE del_department();
pg_restore: creating TRIGGER del_department
pg_restore: [archiver (db)] Error from TOC entry 1634; 16412 22736 TRIGGER del_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_department() does not exist
    Command was: CREATE TRIGGER del_department
    AFTER DELETE ON ap
    FOR EACH ROW
    EXECUTE PROCEDURE del_department();
pg_restore: creating TRIGGER del_department
pg_restore: [archiver (db)] Error from TOC entry 1625; 16412 22737 TRIGGER del_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_department() does not exist
    Command was: CREATE TRIGGER del_department
    AFTER DELETE ON gl
    FOR EACH ROW
    EXECUTE PROCEDURE del_department();
pg_restore: creating TRIGGER del_department
pg_restore: [archiver (db)] Error from TOC entry 1639; 16412 22738 TRIGGER del_department sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_department() does not exist
    Command was: CREATE TRIGGER del_department
    AFTER DELETE ON oe
    FOR EACH ROW
    EXECUTE PROCEDURE del_department();
pg_restore: creating TRIGGER del_exchangerate
pg_restore: [archiver (db)] Error from TOC entry 1631; 16412 22744 TRIGGER del_exchangerate sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_exchangerate() does not exist
    Command was: CREATE TRIGGER del_exchangerate
    BEFORE DELETE ON ar
    FOR EACH ROW
    EXECUTE PROCEDURE del_exchangerate();
pg_restore: creating TRIGGER del_exchangerate
pg_restore: [archiver (db)] Error from TOC entry 1635; 16412 22745 TRIGGER del_exchangerate sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_exchangerate() does not exist
    Command was: CREATE TRIGGER del_exchangerate
    BEFORE DELETE ON ap
    FOR EACH ROW
    EXECUTE PROCEDURE del_exchangerate();
pg_restore: creating TRIGGER del_exchangerate
pg_restore: [archiver (db)] Error from TOC entry 1640; 16412 22746 TRIGGER del_exchangerate sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_exchangerate() does not exist
    Command was: CREATE TRIGGER del_exchangerate
    BEFORE DELETE ON oe
    FOR EACH ROW
    EXECUTE PROCEDURE del_exchangerate();
pg_restore: creating TRIGGER del_recurring
pg_restore: [archiver (db)] Error from TOC entry 1632; 16412 22755 TRIGGER del_recurring sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_recurring() does not exist
    Command was: CREATE TRIGGER del_recurring
    AFTER DELETE ON ar
    FOR EACH ROW
    EXECUTE PROCEDURE del_recurring();
pg_restore: creating TRIGGER del_recurring
pg_restore: [archiver (db)] Error from TOC entry 1636; 16412 22756 TRIGGER del_recurring sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_recurring() does not exist
    Command was: CREATE TRIGGER del_recurring
    AFTER DELETE ON ap
    FOR EACH ROW
    EXECUTE PROCEDURE del_recurring();
pg_restore: creating TRIGGER del_recurring
pg_restore: [archiver (db)] Error from TOC entry 1626; 16412 22757 TRIGGER del_recurring sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_recurring() does not exist
    Command was: CREATE TRIGGER del_recurring
    AFTER DELETE ON gl
    FOR EACH ROW
    EXECUTE PROCEDURE del_recurring();
pg_restore: creating TRIGGER del_vendor
pg_restore: [archiver (db)] Error from TOC entry 1641; 16412 22742 TRIGGER del_vendor sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_vendor() does not exist
    Command was: CREATE TRIGGER del_vendor
    AFTER DELETE ON vendor
    FOR EACH ROW
    EXECUTE PROCEDURE del_vendor();
pg_restore: creating TRIGGER del_yearend
pg_restore: [archiver (db)] Error from TOC entry 1627; 16412 22733 TRIGGER del_yearend sql-ledger
pg_restore: [archiver (db)] could not execute query: ERROR:  function del_yearend() does not exist
    Command was: CREATE TRIGGER del_yearend
    AFTER DELETE ON gl
    FOR EACH ROW
    EXECUTE PROCEDURE del_yearend();
pg_restore: setting owner and privileges for SCHEMA public
pg_restore: setting owner and privileges for COMMENT SCHEMA public
pg_restore: setting owner and privileges for ACL public
pg_restore: setting owner and privileges for FUNCTION plpgsql_call_handler()
pg_restore: setting owner and privileges for PROCEDURAL LANGUAGE plpgsql
pg_restore: setting owner and privileges for FUNCTION avgcost(integer)
pg_restore: setting owner and privileges for FUNCTION check_department()
pg_restore: setting owner and privileges for FUNCTION check_inventory()
pg_restore: setting owner and privileges for FUNCTION del_customer()
pg_restore: setting owner and privileges for FUNCTION del_department()
pg_restore: setting owner and privileges for FUNCTION del_exchangerate()
pg_restore: setting owner and privileges for FUNCTION del_recurring()
pg_restore: setting owner and privileges for FUNCTION del_vendor()
pg_restore: setting owner and privileges for FUNCTION del_yearend()
pg_restore: setting owner and privileges for FUNCTION lastcost(integer)
pg_restore: setting owner and privileges for TABLE acc_trans
pg_restore: setting owner and privileges for TABLE ap
pg_restore: setting owner and privileges for TABLE ar
pg_restore: setting owner and privileges for TABLE assembly
pg_restore: setting owner and privileges for TABLE audittrail
pg_restore: setting owner and privileges for TABLE business
pg_restore: setting owner and privileges for TABLE chart
pg_restore: setting owner and privileges for TABLE customer
pg_restore: setting owner and privileges for TABLE customertax
pg_restore: setting owner and privileges for TABLE defaults
pg_restore: setting owner and privileges for TABLE department
pg_restore: setting owner and privileges for TABLE dpt_trans
pg_restore: setting owner and privileges for TABLE employee
pg_restore: setting owner and privileges for TABLE exchangerate
pg_restore: setting owner and privileges for TABLE gifi
pg_restore: setting owner and privileges for TABLE gl
pg_restore: setting owner and privileges for SEQUENCE id
pg_restore: setting owner and privileges for TABLE inventory
pg_restore: setting owner and privileges for TABLE invoice
pg_restore: setting owner and privileges for SEQUENCE invoiceid
pg_restore: setting owner and privileges for TABLE jcitems
pg_restore: setting owner and privileges for SEQUENCE jcitemsid
pg_restore: setting owner and privileges for TABLE language
pg_restore: setting owner and privileges for TABLE makemodel
pg_restore: setting owner and privileges for TABLE oe
pg_restore: setting owner and privileges for TABLE orderitems
pg_restore: setting owner and privileges for SEQUENCE orderitemsid
pg_restore: setting owner and privileges for TABLE parts
pg_restore: setting owner and privileges for TABLE partscustomer
pg_restore: setting owner and privileges for TABLE partsgroup
pg_restore: setting owner and privileges for TABLE partstax
pg_restore: setting owner and privileges for TABLE partsvendor
pg_restore: setting owner and privileges for TABLE pricegroup
pg_restore: setting owner and privileges for TABLE project
pg_restore: setting owner and privileges for TABLE recurring
pg_restore: setting owner and privileges for TABLE recurringemail
pg_restore: setting owner and privileges for TABLE recurringprint
pg_restore: setting owner and privileges for TABLE shipto
pg_restore: setting owner and privileges for TABLE sic
pg_restore: setting owner and privileges for TABLE status
pg_restore: setting owner and privileges for TABLE tax
pg_restore: setting owner and privileges for TABLE translation
pg_restore: setting owner and privileges for TABLE vendor
pg_restore: setting owner and privileges for TABLE vendortax
pg_restore: setting owner and privileges for TABLE warehouse
pg_restore: setting owner and privileges for TABLE yearend
pg_restore: setting owner and privileges for INDEX acc_trans_chart_id_key
pg_restore: setting owner and privileges for INDEX acc_trans_source_key
pg_restore: setting owner and privileges for INDEX acc_trans_trans_id_key
pg_restore: setting owner and privileges for INDEX acc_trans_transdate_key
pg_restore: setting owner and privileges for INDEX ap_employee_id_key
pg_restore: setting owner and privileges for INDEX ap_id_key
pg_restore: setting owner and privileges for INDEX ap_invnumber_key
pg_restore: setting owner and privileges for INDEX ap_ordnumber_key
pg_restore: setting owner and privileges for INDEX ap_quonumber_key
pg_restore: setting owner and privileges for INDEX ap_transdate_key
pg_restore: setting owner and privileges for INDEX ap_vendor_id_key
pg_restore: setting owner and privileges for INDEX ar_customer_id_key
pg_restore: setting owner and privileges for INDEX ar_employee_id_key
pg_restore: setting owner and privileges for INDEX ar_id_key
pg_restore: setting owner and privileges for INDEX ar_invnumber_key
pg_restore: setting owner and privileges for INDEX ar_ordnumber_key
pg_restore: setting owner and privileges for INDEX ar_quonumber_key
pg_restore: setting owner and privileges for INDEX ar_transdate_key
pg_restore: setting owner and privileges for INDEX assembly_id_key
pg_restore: setting owner and privileges for INDEX audittrail_trans_id_key
pg_restore: setting owner and privileges for INDEX chart_accno_key
pg_restore: setting owner and privileges for INDEX chart_category_key
pg_restore: setting owner and privileges for INDEX chart_gifi_accno_key
pg_restore: setting owner and privileges for INDEX chart_id_key
pg_restore: setting owner and privileges for INDEX chart_link_key
pg_restore: setting owner and privileges for INDEX customer_contact_key
pg_restore: setting owner and privileges for INDEX customer_customer_id_key
pg_restore: setting owner and privileges for INDEX customer_customernumber_key
pg_restore: setting owner and privileges for INDEX customer_id_key
pg_restore: setting owner and privileges for INDEX customer_name_key
pg_restore: setting owner and privileges for INDEX department_id_key
pg_restore: setting owner and privileges for INDEX employee_id_key
pg_restore: setting owner and privileges for INDEX employee_login_key
pg_restore: setting owner and privileges for INDEX employee_name_key
pg_restore: setting owner and privileges for INDEX exchangerate_ct_key
pg_restore: setting owner and privileges for INDEX gifi_accno_key
pg_restore: setting owner and privileges for INDEX gl_description_key
pg_restore: setting owner and privileges for INDEX gl_employee_id_key
pg_restore: setting owner and privileges for INDEX gl_id_key
pg_restore: setting owner and privileges for INDEX gl_reference_key
pg_restore: setting owner and privileges for INDEX gl_transdate_key
pg_restore: setting owner and privileges for INDEX invoice_id_key
pg_restore: setting owner and privileges for INDEX invoice_trans_id_key
pg_restore: setting owner and privileges for INDEX jcitems_id_key
pg_restore: setting owner and privileges for INDEX language_code_key
pg_restore: setting owner and privileges for INDEX makemodel_make_key
pg_restore: setting owner and privileges for INDEX makemodel_model_key
pg_restore: setting owner and privileges for INDEX makemodel_parts_id_key
pg_restore: setting owner and privileges for INDEX oe_employee_id_key
pg_restore: setting owner and privileges for INDEX oe_id_key
pg_restore: setting owner and privileges for INDEX oe_ordnumber_key
pg_restore: setting owner and privileges for INDEX oe_transdate_key
pg_restore: setting owner and privileges for INDEX orderitems_id_key
pg_restore: setting owner and privileges for INDEX orderitems_trans_id_key
pg_restore: setting owner and privileges for INDEX parts_description_key
pg_restore: setting owner and privileges for INDEX parts_id_key
pg_restore: setting owner and privileges for INDEX parts_partnumber_key
pg_restore: setting owner and privileges for INDEX partsgroup_id_key
pg_restore: setting owner and privileges for INDEX partsgroup_key
pg_restore: setting owner and privileges for INDEX partstax_parts_id_key
pg_restore: setting owner and privileges for INDEX partsvendor_parts_id_key
pg_restore: setting owner and privileges for INDEX partsvendor_vendor_id_key
pg_restore: setting owner and privileges for INDEX pricegroup_id_key
pg_restore: setting owner and privileges for INDEX pricegroup_pricegroup_key
pg_restore: setting owner and privileges for INDEX project_id_key
pg_restore: setting owner and privileges for INDEX projectnumber_key
pg_restore: setting owner and privileges for INDEX shipto_trans_id_key
pg_restore: setting owner and privileges for INDEX status_trans_id_key
pg_restore: setting owner and privileges for INDEX translation_trans_id_key
pg_restore: setting owner and privileges for INDEX vendor_contact_key
pg_restore: setting owner and privileges for INDEX vendor_id_key
pg_restore: setting owner and privileges for INDEX vendor_name_key
pg_restore: setting owner and privileges for INDEX vendor_vendornumber_key
pg_restore: setting owner and privileges for INDEX vendortax_vendor_id_key
pg_restore: setting owner and privileges for TRIGGER check_department
pg_restore: setting owner and privileges for TRIGGER check_department
pg_restore: setting owner and privileges for TRIGGER check_department
pg_restore: setting owner and privileges for TRIGGER check_department
pg_restore: setting owner and privileges for TRIGGER check_inventory
pg_restore: setting owner and privileges for TRIGGER del_customer
pg_restore: setting owner and privileges for TRIGGER del_department
pg_restore: setting owner and privileges for TRIGGER del_department
pg_restore: setting owner and privileges for TRIGGER del_department
pg_restore: setting owner and privileges for TRIGGER del_department
pg_restore: setting owner and privileges for TRIGGER del_exchangerate
pg_restore: setting owner and privileges for TRIGGER del_exchangerate
pg_restore: setting owner and privileges for TRIGGER del_exchangerate
pg_restore: setting owner and privileges for TRIGGER del_recurring
pg_restore: setting owner and privileges for TRIGGER del_recurring
pg_restore: setting owner and privileges for TRIGGER del_recurring
pg_restore: setting owner and privileges for TRIGGER del_vendor
pg_restore: setting owner and privileges for TRIGGER del_yearend
WARNING: errors ignored on restore: 45

Process returned exit code 1.


----- Vladimir Botka <vl...@bo...> wrote:
> > 
> > Hello all i am migrating from freebsd 4.11 to 6.2 this includes a
> > sql-ledger migration/update. 
> > 
> > I was running version 
> > sql-ledger 2.6.16 i think but it is broken now so i cannot really
> say
> > for certain. 
> > 
> > postgresql-server-7.4.13_1 
> > 
> > now i am running 
> > postgresql-server-7.4.16 
> > sql-ledger-2.6.26 
> > 
> > As stated above i have succesfully installed the versions of
> > sql-ledger and postgres that i need. 
> > 
> > My problem lies with getting the old database into the new postgres
> i
> > have exported without error but when i try to import it i come
> across
> > all sorts of errors nonresistant database nonresistant user
> language
> > problems . Could someone kindly help me with this as i have been
> > struggling with it for days now. 
> > 
> > thanks in advance 
> 
> Hello,
> pg_dump and pg_restore should work. If not so post the errors.
> Generally:
> 1. install OS & SL
> 2. dump and restore the database
> 3. maybe upgrade SL again
> 
> Cheers, -vlado


-- 
Computer King & CaN Mail  -  Sales Service Hosting Backup

http://www.computerking.ca     http://www.canmail.org

NEW!!! Custom Service Packages
Secure IMAP Email - Automated Remote Backups - Photo Blogs - Online Accounting Packages 

[SL] SL 2.8 General questions

[Dirk E. S. <ds...@ca...>]

Before final update I did a test install of version 2.8 to play&test in a
test environment. - I guess some people on this list are doing the same or
have migrated already. I have several questions:

-Under shipping the "Transfer Inventory" does not appear anymore. Has this
been replaced? How do you transfer inventory in 2.8?

-Vouchers: What do you use vouchers for? How do you use it?

- Early payment discount: How do you apply it? I can see the field in the
payment module but I can't insert a value.

- Payment scheduling: Any hints how to do this?

- The SQL-Ledger website says: "variable replacement for description,
notes, internal notes and email message now include first and last day,
month, day and year" - does this mean I can sent out recurring
transactions with cahnging descriptions? Like "Rent $month $year"?

-How can I set the rounding?

-On the invoices screen I can see a checkbox besides of description. What
does this checkbox do?

Thanks for any hints & tips!

Enrique

-- 
Dirk Enrique Seiffert - Lintec S.A.
Ed. Torre del Reloj - Of. 401
Plaza de los Coches, Centro
Cartagena - Colombia
http://www.lintecsa.com

Re: [SL] Reconciliation mismatch

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

On Wed, 11 Apr 2007, Jeff Roberts wrote:

>>
>> Before you add a transaction click on "Done".
> If you try to hit 'Done' without the missing transactions it is out of
> balance and will not let you proceed unless you falsify the 'statement
> balance' to match the ledger balance.

statement balance from bank statement - missing transactions = new 
statement balance.

The new statement balance is not falsifying the statement balance, it is 
simply to make the statement balance to be the statement balance without 
the missing transactions.

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

Re: [SL] Reconciliation mismatch

[Mark L. <mar...@in...>]

Or, just make sure you've entered those miscellaneous transactions  
prior to reconciling

On Apr 11, 2007, at 11:06 PM, Jeff Roberts wrote:

>>
>> Before you add a transaction click on "Done".
> If you try to hit 'Done' without the missing transactions it is out of
> balance and will not let you proceed unless you falsify the 'statement
> balance' to match the ledger balance.
>
> I guess this isn't a big deal as long as it's known that adding a
> transaction 'mid - reconciliation' will screw up the rec index. It
> really had me scratching my head for a while before I discovered what
> had happened.
>
> Jeff Roberts
> JR Electronics
>
>
> Dieter Simader wrote:
>> The checkmarks are kept track of with an index. If you insert a
>> transaction it will mess up things. Before you add a transaction  
>> click on
>> "Done". When you recall the reconciliation screen the checkmarks  
>> will be
>> set for the ones you reconciled already.
>>
>>
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

[SL] 2.8.0 bugs

[Mark L. <mar...@in...>]

I've noticed a bug with the 2.8.0 release and I'm wondering if anyone  
else has encountered it.

On the payments screen:  I'm trying to pay two vendor invoices from  
the list of vendors we owe money to.  I selected the first vendor and  
the last vendor on the list.  When I printed the checks, the first  
vendor's check printed correctly.  However, the second check had the  
correct amount on it (for the selected vendor), but the pay to was  
filled out for a different vendor entirely.

Thanks!
Mark

Re: [SL] My 2 cents

[George O. <geo...@ya...>]

After upgrade to 2.8.0 I noticed I have a difference of $0.02 between Debit 
and Credit numbers in my COA. Is this something I should bother investigating 
(like a sign of a bigger problem for example)? It is only 2 cents but I never 
had any balance problems before.


-- 
George
AUSTRALIA
http://www.okstudio.com.au

Re: [SL] Reconciliation mismatch

[Jeff R. <je...@jr...>]

>
> Before you add a transaction click on "Done".
If you try to hit 'Done' without the missing transactions it is out of 
balance and will not let you proceed unless you falsify the 'statement 
balance' to match the ledger balance.

I guess this isn't a big deal as long as it's known that adding a 
transaction 'mid - reconciliation' will screw up the rec index. It 
really had me scratching my head for a while before I discovered what 
had happened.

Jeff Roberts
JR Electronics


Dieter Simader wrote:
> The checkmarks are kept track of with an index. If you insert a 
> transaction it will mess up things. Before you add a transaction click on 
> "Done". When you recall the reconciliation screen the checkmarks will be 
> set for the ones you reconciled already.
>
>   

Re: [SL] Reconciliation mismatch

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

The checkmarks are kept track of with an index. If you insert a 
transaction it will mess up things. Before you add a transaction click on 
"Done". When you recall the reconciliation screen the checkmarks will be 
set for the ones you reconciled already.

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

On Wed, 11 Apr 2007, Jeff Roberts wrote:

> Hi This may be an odd one but I'll try to explain it the best I can.
>
> I open the reconciliation page and select my bank account and up pop all
> un-reconciled transactions.
> I reconcile (by ticking) all the transactions that appear on my statement.
> I then usually have a few transactions on my statement that have not
> been entered yet (bank charges, interest etc)
> I use "open in a new tab" from the side menu bar to get another tab
> (Firefox) with AP transactions.
> I then enter the missing transactions, print and post them and close the
> extra tab which puts me back at my original tab.
> The new transactions aren't showing yet so I hit 'update' and the list
> refreshes and now the new transactions are showing.
>
> Here's where the oddity occurs, when the page adds the new transactions
> it doesn't keep the 'tick' marks with the reconciled transactions, they
> go out of sync.
>
> If I add two transactions say one from the 15th of the month and one
> from the 21st, they appear in the list in the correct order but the last
> two transactions in the list are now 'unticked' and the order from the
> 15th to the end of the month is out of sequence. It's as if when the
> page is refreshed the data of the 'tick' is not correlated to the
> transaction it is beside.
>
> I just confirmed it on the Edmonton demo, the last transaction is to
> CASH dated 10 May 2007, the second to last transaction was to Smith P
> dated 04 May 2007. I ticked both transactions. Then I opened a new tab
> and entered a new transaction (Fred Company) dated 05 May 2007 (between
> the two) and when I hit 'update' it refreshes but now CASH is on the
> last line and it is unticked while the new transaction is on the second
> to last line and it is ticked! It now looks like Fred Company has been
> reconciled but CASH hasn't.
>
> Any ideas on how to correct this?
>
> Jeff Roberts
> JR Electronics
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

[SL] Reconciliation mismatch

[Jeff R. <je...@jr...>]

Hi This may be an odd one but I'll try to explain it the best I can.

I open the reconciliation page and select my bank account and up pop all 
un-reconciled transactions.
I reconcile (by ticking) all the transactions that appear on my statement.
I then usually have a few transactions on my statement that have not 
been entered yet (bank charges, interest etc)
I use "open in a new tab" from the side menu bar to get another tab 
(Firefox) with AP transactions.
I then enter the missing transactions, print and post them and close the 
extra tab which puts me back at my original tab.
The new transactions aren't showing yet so I hit 'update' and the list 
refreshes and now the new transactions are showing.

Here's where the oddity occurs, when the page adds the new transactions 
it doesn't keep the 'tick' marks with the reconciled transactions, they 
go out of sync.

If I add two transactions say one from the 15th of the month and one 
from the 21st, they appear in the list in the correct order but the last 
two transactions in the list are now 'unticked' and the order from the 
15th to the end of the month is out of sequence. It's as if when the 
page is refreshed the data of the 'tick' is not correlated to the 
transaction it is beside.

I just confirmed it on the Edmonton demo, the last transaction is to 
CASH dated 10 May 2007, the second to last transaction was to Smith P 
dated 04 May 2007. I ticked both transactions. Then I opened a new tab 
and entered a new transaction (Fred Company) dated 05 May 2007 (between 
the two) and when I hit 'update' it refreshes but now CASH is on the 
last line and it is unticked while the new transaction is on the second 
to last line and it is ticked! It now looks like Fred Company has been 
reconciled but CASH hasn't.

Any ideas on how to correct this?

Jeff Roberts
JR Electronics

[SL] Reconliation of past transactions

[Ryan J. <ry...@ne...>]

Hey,

The new reconciliation features don't allow you to filter out
transactions that don't lie within the specified reconciliation date
range that haven't been reconciled.

Is there a quick way to clear a past transactions without effecting the
current balance?

Cheers,
Ryan

Re: [SL] receipt printer

[C. D. H. <Du...@Du...>]

We don't use the POS, but we do have 3 Zebra thermal printers working w/ 
SQL-Ledger - a parallel 2443, a 2844 and a 2824 which are both 
ethernet.  We run thermal labels through all of them but you could run 
thermal roll paper through for receipts.  The standard CUPS Zebra driver 
supports all of them.

Dunc

Arthur Dyck wrote:
> I've just begun exploring the use of SL for our non-profit society.  One
> of the reasons I have been looking at SL is because of the integrated
> POS.  Does anyone have any recommendations for a receipt printer that is
> going to work out of the box?
>
> Arthur
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>   

[SL] receipt printer

[Arthur D. <ar...@av...>]

I've just begun exploring the use of SL for our non-profit society.  One
of the reasons I have been looking at SL is because of the integrated
POS.  Does anyone have any recommendations for a receipt printer that is
going to work out of the box?

Arthur

[SL] New national currency

[R. Q. <rq...@gm...>]

Ghana will change her currency from Cedis (CED) to New Ghana cedis 
(NGC), starting from 1st July 2007.
10,000 CED = 1 GHC.
Both currencies will be used parallel for some time for the next six months.
How do I change my default currency and how will it affect my 
transactions/accounts?
Regards
Robert

[SL] Invoice.tex - path / relative path to images?? Using a <%variable%>??

[Stroller <lin...@my...>]

Hi there,

After a recent hard-drive failure on my server I'm currently redoing  
the layout of my invoice.tex
I had been foresighted enough to do a daily pg_dumpall & email the  
results to myself (saving a copy on my desktop PC) but had not  
thought to backup this important file!! :(

Anyway, if I make the following minimum case invoice template & email  
an invoice to myself, only the first image (A:) is shown:

   \documentclass{minimal}
   \usepackage[a4paper,landscape,dvips]{geometry}
   \geometry{a4paper,landscape,
             nohead,nofoot,
             left=15mm,right=15mm,top=1cm,bottom=1cm}
   \usepackage{graphicx}
   \usepackage{ifpdf}
   \begin{document}
   \thispagestyle{empty}
   \noindent

   A:
   \includegraphics[scale=1]{/usr/local/sql-ledger/templates/stroller/ 
logo-colour}

   B:
   \includegraphics[scale=1]{./logo-colour}

   C:
   \includegraphics[scale=1]{logo-colour}

   \end{document}

In the default letterhead.tex the path to the image files is defined  
as "../<%templates%>/<%language_code%>/logo". Is there some similar  
variable which allows me to say "../stroller/logo"? EG: ../<%user%>/ 
logo"? I have tried <%user%>, <%employee%> and <%employee_id%>, none  
of which work, but I thought there might be another variable I'm not  
aware of?

Strangely, if I compile the invoice.tex manually (I tend just to use  
`rubber --pdf /usr/local/sql-ledger/templates/stroller/invoice.tex`)  
then LaTeX only b0rks out on the _second_ image (B:). Even though I'm  
working from my home directory, "\includegraphics[scale=1]{logo- 
colour}" seems to look in the same directory as that in which  
the .tex file resides - "./logo-colour" appears to look in the  
current working directory (which is what I would have expected from  
C:, too, to be honest).

Any suggestions?

Stroller.

[SL] 2.8.0 invoice.tex error depends on user settings

[Philippe J. <pj...@po...>]

since upgrade from 2.6 to 2.8 I get errors in invoice.tex printing due 
to underscore and % characters

When I use French-utf8 (or other except english) as preference user 
setting I get a wrong behaviour; with english setting I get the correct 
printing of the same invoice.tex

-- 
Salutations Philippe JAOUEN	 GnuPG Key ID: 0xD103AAA8
Ferme du Ponctey :               http://www.ponctey.fr
cidre fermier du Pays de La Risle, Pommeau de Normandie et Calvados AOC

Re: [SL] DBD-pg.zip

[ATM L. <atm...@km...>]

Not sure if this is any help at all, however I normally install via cpan>
install DBD::Pg and in the past I have had issues to to the following:

Trying DBD::pg does not work, 
and copy pasting will sometimes give you the DBD:[the Razz Smiley Picture
:P] and then g

Hope its something simple like this for ya.

---Andrew

 

> -----Original Message-----
> From: sql...@li... 
> [mailto:sql...@li...] On 
> Behalf Of Mike Cinquino
> Sent: Monday, April 09, 2007 7:29 AM
> To: sql...@li...
> Subject: [SL] DBD-pg.zip
> 
> I would like to give sql-ledger a try but the link in the 
> install manual to get DBD-pg.zip is not working. I get a 404 
> not found error. Is there another location to get this file from. 
> 
> Thanks,
> Mike
> 
> 
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT Join 
> SourceForge.net's Techsay panel and you'll get the chance to 
> share your opinions on IT & business topics through brief 
> surveys-and earn cash 
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
> &CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> 

[SL] The name Bank of the client in the invoice?

[<ig...@3d...>]

I'm playing with SQL-LEDGER to understand is it useful for me or not. It =
looks interesting but I have faced a problem to prepare required forms =
and the data.

As I see there is place in customers data for IBAN account but where I =
can put the Bank name? Also I need to place  the Bank name and IBAN in =
the invoice, if this is possible?

The second question about format of date. Currently the date in the =
invoice looks like 19-02-2007 but I need to make it like 19 February =
2007. Is this possible to customize the date format?

Thanks

Igor

[SL] DBD-pg.zip

[Mike C. <mci...@di...>]

I would like to give sql-ledger a try but the link in the install manual
to get DBD-pg.zip is not working. I get a 404 not found error. Is there
another location to get this file from. 

Thanks,
Mike