Oops, I meant Dennis, not B.D. Hey Dennis, how would that linking table look? Just the 3 columns, maybe with some dateon and dateoff columns?
bill On Wed, May 30, 2012 at 8:24 AM, Dennis McGrath <[email protected]> wrote: > In this situation, I would have a Family table, an Individual Table, and a > FamilyLink table**** > > The FamilyLink table would have its own ID column along with FamilyID and > IndividulID.**** > > ** ** > > This allows you to have one family with many members and one member as > part of many families.**** > > Then you could bill to the correct FamilyLinkIDs referencing the correct > family/individual combinations.**** > > ** ** > > ** ** > > ** ** > > Dennis McGrath**** > > Software Developer**** > > QMI Security Solutions**** > > 1661 Glenlake Ave**** > > Itasca IL 60143**** > > 630-980-8461**** > > [email protected]**** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *J > BLAUSTEIN > *Sent:* Wednesday, May 30, 2012 9:57 AM > *To:* RBASE-L Mailing List > *Subject:* [RBASE-L] - Re: accounting question; medical billing systems*** > * > > ** ** > > Bill > Add a family id with a separate user id - then you can bill either on a > family base or individual and print reports on either level > J > On 5/29/2012 7:44 PM, William Stacy wrote: **** > > I'm restructuring my billing system to become more flexible and correct > and would appreciate any suggestions/pointers from those more skilled than > I. My restructure is mostly due to two things. One, I've always billed by > family accounts, where one family member is assigned as the account > holder. The problem arises now and then that a family member leaves the > nest and either then has their own account, or joins another family which > has its own account. > > The problem is with the old transactions of prior family members not > showing up in account lookbacks. > > I know one popular way is to have everyone have their own accounts and > just split family payments into their individual parts. It's not pretty, > and requires more computing and more complex statements, but it would > solve the problem. > > I've also been toying with handling it at the transaction line item level, > assigning a permanent bill-to person/entity at that level which can also be > used to handle 3rd party issues. Which is the other part of this > restructure. > > TIA > > Bill > > > > -- > William Stacy, O.D. > > Please visit my website by clicking on : > > http://www.folsomeye.net > > > **** > > ** ** > > -- > > **** > > *J. Blaustein***** > > *J Blaustein Associates, Inc.***** > > * 12 Herrick Drive***** > > * Lawrence, NY 11559***** > > *516-371-3445 FAX 516-345-8009***** > -- William Stacy, O.D. Please visit my website by clicking on : http://www.folsomeye.net
