On 6/20/07, Jeff Kowalczyk <[EMAIL PROTECTED]> wrote:
> --- Ed W <[EMAIL PROTECTED]> wrote:
> > contacts with a structured history trail
> > (...)
> > I think it's helpful to review the
> > kind of "use cases" that I sketched out and perhaps dream up some more -
> > I think it helps figure out if w
--- Ed W <[EMAIL PROTECTED]> wrote:
> contacts with a structured history trail
> (...)
> I think it's helpful to review the
> kind of "use cases" that I sketched out and perhaps dream up some more -
> I think it helps figure out if we have got the model right if we see
> that we can do all the o
Jeff Kowalczyk wrote:
--- [EMAIL PROTECTED] wrote:
+1. An argument could even be made that an invoice, once produced,
should become an opaque blob of data. I can't think of any reason to
modify a produced invoice. Any amending of an invoice should surely
create a new, separate documen
On 6/20/07, Jeff Kowalczyk <[EMAIL PROTECTED]> wrote:
>
> --- [EMAIL PROTECTED] wrote:
> > +1. An argument could even be made that an invoice, once produced,
> > should become an opaque blob of data. I can't think of any reason to
> > modify a produced invoice. Any amending of an invoice should
--- [EMAIL PROTECTED] wrote:
> +1. An argument could even be made that an invoice, once produced,
> should become an opaque blob of data. I can't think of any reason to
> modify a produced invoice. Any amending of an invoice should surely
> create a new, separate document?
True, that rev
Quoting Shaun Laughey <[EMAIL PROTECTED]>:
> +1 to Stroller - every good system I've used, designed or pleased to pay
> for has had the invoice address and other details recorded against the
> invoice not the customer.
>
> It may copy them from the customer at invoice time but after that they
>
On Wed, 2007-06-20 at 11:52 +0100, Stroller wrote:
> On 20 Jun 2007, at 06:04, Chris Travers wrote:
> > ...
> > I understand what you are saying, but I still disagree. Instead I
> > think we are talking two different things.
> >
> > 1) Invoices need to be entirely self-contained. They need to sto
On 20 Jun 2007, at 06:04, Chris Travers wrote:
> ...
> I understand what you are saying, but I still disagree. Instead I
> think we are talking two different things.
>
> 1) Invoices need to be entirely self-contained. They need to store
> all information required to recreate and track them. We
