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

[Matt B. <ma...@li...>]

I have to say, I think the "employee also your customer" notion is
somewhat strained.  I doubt it leads to much data redundancy.

Offhand, possibly "your vendor is also your customer" is more common, and
maybe is more relevant.


matt


Matt Benjamin President/CTO

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

tel. 734-761-4689
fax. 734-769-8938
pgr. 734-431-0118

On Thu, 10 May 2001, Wayne wrote:

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