On Thu, Oct 2, 2014 at 11:55 PM, <
ledger-smb-users-requ...@lists.sourceforge.net> wrote:
> Send Ledger-smb-users mailing list submissions to
> ledger-smb-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
> or, via email, send a message with subject or body 'help' to
> ledger-smb-users-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> ledger-smb-users-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ledger-smb-users digest..."
>
>
> Today's Topics:
>
> 1. Re: setup error (Bill Appelbe)
> 2. Chart of Account Query (R. Ransbottom)
> 3. Re: Chart of Account Query (Chris Travers)
> 4. Printing (Bill Appelbe)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 2 Oct 2014 09:13:20 +0100
> From: Bill Appelbe <bappe...@gmail.com>
> Subject: Re: [Ledger-smb-users] setup error
> To: ledger-smb-users@lists.sourceforge.net
> Message-ID:
> <
> cagyw+papsivgau2m2tj106hw4mztu-1xt8tfu25ri0ci3r1...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks
> I had thought that the user was for each company
>
> Bill
>
> On Thu, Oct 2, 2014 at 2:18 AM, Chris Travers <chris.trav...@gmail.com>
> wrote:
>
> > https://github.com/ledgersmb/LedgerSMB/pull/401 corrects this problem.
> >
> > On Wed, Oct 1, 2014 at 5:45 PM, Chris Travers <chris.trav...@gmail.com>
> > wrote:
> >
> >> Hi Bill:
> >>
> >> I fixed a similar issue in the main application and apparently neglected
> >> to fix it here. This is a problem with error handling. It is supposed
> to
> >> handle the error more gracefully. I will get a fix in for 1.4.3 today.
> >> The desired behavior is to notify the user and present the form again
> with
> >> the import option selected.
> >>
> >> In the mean time, this happens when the user already exists in the
> >> database cluster. If you are importing the user, select the 'yes' radio
> >> button while creating the user. In this case you can leave the password
> >> blank and it will nto change the password or set an expiration. This
> >> allows the sharing of accounts between databases, but we naturally don't
> >> want to do this in a way which makes it too easy for users to be
> >> accidentally shared.....
> >>
> >>
> >>
> >> On Wed, Oct 1, 2014 at 1:33 PM, Pongr?cz Istv?n <
> >> pongracz.ist...@gmail.com> wrote:
> >>
> >>>
> >>> Hi,
> >>>
> >>> If you try to add the same user to the system, which exists in other
> >>> instances on the same postgresql, you have to select *import* option.
> >>>
> >>> This is because the user is system wide in the database level and
> linked
> >>> to one or more ledgersmb databases. If the username does not exist, itt
> >>> will be created (system wide) and linked to this database.
> >>>
> >>> Could you confirm, that username existed in your database and you did
> >>> not select import on creating?
> >>>
> >>> Cheers,
> >>>
> >>> Istv?n
> >>>
> >>>
> >>>
> >>> ----------------eredeti ?zenet-----------------
> >>> Felad?: "Bill Appelbe" <bappe...@gmail.com>
> >>> C?mzett: ledger-smb-users@lists.sourceforge.net
> >>> D?tum: Wed, 1 Oct 2014 17:35:09 +0100
> >>> ----------------------------------------------------------
> >>>
> >>>
> >>> Hi
> >>> while creating a new company I got an error in LedgerSMB 1.4.2
> >>> I go through the setup.pl steps and when it press "create user" I get
> >>> Error!
> >>>
> >>>
> >>> *Error from Function: ERROR: Duplicate user More information has been
> >>> reported in the error logs at LedgerSMB.pm line 775. *
> >>>
> >>> dbversion: 1.4.2, company:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> I attach the postgres and apache log file extracts for this.
> >>>
> >>> I have been playing a lot with the database in another company - but
> >>> that shouldn't cause this - or would it?
> >>>
> >>>
> >>>
> >>> Bill
> >>> ------------------------------
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> Reports
> >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog
> Analyzerhttp://
> pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> >>>
> >>> ------------------------------
> >>>
> >>> _______________________________________________
> >>> Ledger-smb-users mailing listLedger-smb-users
> @lists.sourceforge.nethttps://
> lists.sourceforge.net/lists/listinfo/ledger-smb-users
> >>>
> >>>
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> Reports
> >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >>>
> >>>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> >>> _______________________________________________
> >>> Ledger-smb-users mailing list
> >>> Ledger-smb-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
> >>>
> >>>
> >>
> >>
> >> --
> >> Best Wishes,
> >> Chris Travers
> >>
> >> Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
> >> lock-in.
> >> http://www.efficito.com/learn_more
> >>
> >
> >
> >
> > --
> > Best Wishes,
> > Chris Travers
> >
> > Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
> > lock-in.
> > http://www.efficito.com/learn_more
> >
> >
> >
> ------------------------------------------------------------------------------
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Ledger-smb-users mailing list
> > Ledger-smb-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Thu, 2 Oct 2014 08:20:17 -0400
> From: "R. Ransbottom" <rir...@comcast.net>
> Subject: [Ledger-smb-users] Chart of Account Query
> To: ledger-smb-users@lists.sourceforge.net
> Message-ID: <20141002122017.GA6003@vaph.private>
> Content-Type: text/plain; charset=us-ascii
>
> Hello,
>
> Regarding CoA implementation:
>
> Can a account_heading be referenced by discontiguous accounts.
> My experience indicates that discontiguous records are
> GAAP-improper.
>
> By discontiguous I mean, given (100 Cash), (110 Petty Cash),
> (130 A/R), that (100) and (130) have one account_heading parent
> while (110) has a different one.
>
>
> Thanks,
> Rob
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 2 Oct 2014 05:40:40 -0700
> From: Chris Travers <chris.trav...@gmail.com>
> Subject: Re: [Ledger-smb-users] Chart of Account Query
> To: LedgerSMB Users <ledger-smb-users@lists.sourceforge.net>,
> rir...@comcast.net
> Message-ID:
> <CAKt_Zfs0=03zKopUFnJXzFzXUoYe9S1=
> g3cahp-rzszi56z...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Thu, Oct 2, 2014 at 5:20 AM, R. Ransbottom <rir...@comcast.net> wrote:
>
> > Hello,
> >
> > Regarding CoA implementation:
> >
> > Can a account_heading be referenced by discontiguous accounts.
> > My experience indicates that discontiguous records are
> > GAAP-improper.
> >
>
> For reasons below, we can't enforce a contiguousness rule very well.
> However, as you point out breaking that rule on a logical level is
> dangerous.
>
> >
> > By discontiguous I mean, given (100 Cash), (110 Petty Cash),
> > (130 A/R), that (100) and (130) have one account_heading parent
> > while (110) has a different one.
> >
>
> I can't imagine a case where you'd want to do that, unless you wanted to be
> able to aggregate a bunch of petty cash drawers together, and have that
> header have its parent be the same as for 100 and 130.
>
> Let's look at a more likely example:
>
> heading 13000 Accounts Payab,e
> - 13000-00-00 Accounts Payable Corporate
> - 13001 -- Heading: Clients Payable
> -- 13001-00-01 - Clients Payable US
> -- 13001-00-02 - Clients Payable MX
> -- 13001-00-03 - Clients Payable CA
> - 13002 -- Reserves Payable
> -- 13002-00-01 - Reserves Payable US
> -- 13002-00-02 - Reserves Payable MX
> -- 13002-00-04 - Reserves Payable CA
> - 13999-00-00 Accounts Payable Misc
>
> I can think of cases where people have books which are logically like this,
> where everything contiguously is descended from the same header, but may
> not be directly so. Consequently, the subtotal of the 13000 heading will
> be the exact same whether or not the 13001 and 13002 headings are in place,
> but these provide some intermediate points of aggregation which may or may
> not be helpful.
>
> I am not aware of any GAAP issues with the above setup, because 13000
> aggregates represents a contiguous block of accounts. supporting this use
> case, however, does mean we can't enforce things remarkably strictly so
> people can mess up their books.
>
> It is further worth noting that generally there are plenty of places where
> we assume that these blocks are contiguous. We certainly do not consider
> it good practice to break that rule.
>
> >
> >
> > Thanks,
> > Rob
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Ledger-smb-users mailing list
> > Ledger-smb-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
> >
>
>
>
> --
> Best Wishes,
> Chris Travers
>
> Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
> lock-in.
> http://www.efficito.com/learn_more
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Thu, 2 Oct 2014 16:54:50 +0100
> From: Bill Appelbe <bappe...@gmail.com>
> Subject: [Ledger-smb-users] Printing
> To: ledger-smb-users@lists.sourceforge.net
> Message-ID:
> <CAGyw+pb+JDdovcfhoG3Pq_9YWVimq=
> hlgkeck9ltsgbxxq1...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi
> I have been trying to set up printing on my install of LedgerSMB 1.4.2 on
> Linux Mint 17.
> for starters I needed to install package libtex-encode-perl (which as far
> as I can see is not in the install instructions).
>
> Now I am trying to print a sales order that I have to PDF, Screen. I am
> getting the error below.
>
> Am I missing something obvious?
>
> thanks
>
> Bill
>
> Error!
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *'Attribute (format) is required at
> /usr/local/lib/perl/5.18.2/Moose/Exception.pm line 34
>
> Moose::Exception::_build_trace('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)')
> called at reader Moose::Exception::trace (defined at
> /usr/local/lib/perl/5.18.2/Moose/Exception.pm line 6) line 7
>
> Moose::Exception::trace('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)')
> called at /usr/local/lib/perl/5.18.2/Moose/Exception.pm line 46
>
> Moose::Exception::BUILD('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)',
> 'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Class/MOP/Method.pm
> line 123 Class::MOP::Method::execute('Moose::Meta::Method=HASH(0x8dfec10)',
> 'Moose::Exception::AttributeIsRequired=HASH(0x837fda0)', 'HASH(0x8616a30)')
> called at /usr/local/lib/perl/5.18.2/Moose/Object.pm line 52
>
> Moose::Object::BUILDALL('Moose::Exception::AttributeIsRequired=HASH(0x837fda0)',
> 'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Moose/Meta/Class.pm
> line 278
> Moose::Meta::Class::new_object('Moose::Meta::Class=HASH(0x86dd0d8)',
> 'HASH(0x8616a30)') called at /usr/local/lib/perl/5.18.2/Moose/Object.pm
> line 23 Moose::Object::new('Moose::Exception::AttributeIsRequired',
> 'params', 'HASH(0x8648a28)', 'class_name', 'LedgerSMB::Template::DB',
> 'attribute_name', 'format') called at constructor
> LedgerSMB::Template::DB::new (defined at LedgerSMB/Template/DB.pm line 170)
> line 30 LedgerSMB::Template::DB::new('LedgerSMB::Template::DB',
> 'HASH(0x86dd348)') called at LedgerSMB/Template/DB.pm line 68
> LedgerSMB::Template::DB::get_template('LedgerSMB::Template::DB',
> 'envelope', undef, 'tex') called at LedgerSMB/Template/LaTeX.pm line 140
> LedgerSMB::Template::LaTeX::process('LedgerSMB::Template=HASH(0x85cecf8)',
> 'HASH(0x876d0f8)') called at LedgerSMB/Template.pm line 351
> LedgerSMB::Template::render('LedgerSMB::Template=HASH(0x85cecf8)',
> 'Form=HASH(0x2593708)') called at bin/io.pl <http://io.pl> line 1994
> lsmb_legacy::print_form(undef) called at bin/io.pl <http://io.pl> line
> 1578
> lsmb_legacy::print at old-handler.pl <http://old-handler.pl> line 206
> lsmb_legacy::try {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 81
> eval {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 72
> Try::Tiny::try('CODE(0x26ed950)', 'Try::Tiny::Catch=REF(0x79ddd50)') called
> at old-handler.pl <http://old-handler.pl> line 225 require old-handler.pl
> <http://old-handler.pl> at /usr/share/ledgersmb/oe.pl <http://oe.pl> line
> 7'*
>
> dbversion: 1.4.2, company:
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> Ledger-smb-users mailing list
> Ledger-smb-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>
>
>
> End of Ledger-smb-users Digest, Vol 97, Issue 5
> ***********************************************
>
Did you install live-latex recommended?
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
