Joshua D. Drake wrote: >> I suppose that once we go to an AJAX-based interface, we could >> accomodate that case fairly easily. However in the mean time, it is >> going to be difficult to balance data flexibility with workflow. So >> in order to avoid data management issues, I am going to suggest that >> for the time being, we enforce a 1:1 relationship between contacts, >> addresses, phone_numbers, addresses, and email_addresses. This should >> cut down on bugs until we get to the point where we can remove this >> (albeit arbitrary) restriction without interfering too much with >> workflow. > > That seems a bit of a bear. I would prefer to have a primary address > which displays per the workflow issue. The other addresses you can grab > if you need.
I second this suggestion. Too many of my clients have a need for multiples of each. Charley ------------------------------------------------------------------------- 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
