Quoting Shaun Laughey <[EMAIL PROTECTED]>: <snippety>
> +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 > become part of the invoice. > > I think the use of linked lists is a complication that isn't really > needed here. +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? Cheers, Richard ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
