On 3/14/07, Charley Tiggs <[EMAIL PROTECTED]> wrote: > > I second this suggestion. Too many of my clients have a need for > multiples of each.
Multiple addresses per contact? Or multiple addresses per company? The reason I ask is that until we get something AJAX-based, handling multiples of anything per anything else is going to require extra workflow steps. My understanding (correct me if I am wrong, Joshua) at least to allow multiple contacts per company in 1.3 and allow within the db other data to be stored. And then in 2.0 when we are able to move to an AJAX model, allow multiple addresses, phone numbers, email addresses, etc. per contact from the workflow provided. Of course that might just be a default, and it might not be too hard to add that in for customers who really needed it. But the number of round-trips might get annoying ;-) Best Wishes, Chris Travers ------------------------------------------------------------------------- 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 _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
