Insurance Module corrected - Microsoft Access Forum


	Back to Access Forum Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

Insurance Module corrected

Eduardo Benaim

3 years ago

I am following your ABCD and now your Association DB development.
I am very interested in an "Insurance Database" in the image of "Associations DB" or "ABCD DB".
Insurance is very Interesting. It may have Individuals alone or in families and may be in Companies or alone.
The insurance Products can be for individuals, families, or Companies.
For example: a Family can have A Health insurance Plan for all or different ones for everyone.
A Company may have different Plans for its employees and their Families.
Products are Health, Medicare, Life, Dental, Vision, Legal, Accident etc.
The most important thing is to get the initial database Design right.
I believe that ABCD or Associations are not right for Insurance as they are.
I am willing to help in the Design of a Solid Database to include all this or see you develop it.
The key is to understand the Grouping: "Individual --> Family--> Company ". AS in the Associations one should be able to enter.
by any of the Three. Associations does Family and Individuals and Need to add Companies.
I have a working Database that have been developing for 8 years which has been growing. (Lots of queries and Macros)
I need to make a more efficient Database from the Ground up. I have been waiting for your Products so I can stay consistent.
In my Database I have used your: SQL, VBA, email, Login, Updater, and some other lessons. It is time renew.

	Alex Hedley @Reply 3 years ago
Ref for others, links to courses: Association 1 and ABCD

	Eduardo Benaim OP @Reply 3 years ago
Alex. I do not understand why you are pointing me back to the Databases that I am mentioning in the first line of my request. I have studied them both carefully: Association and ABCD. These databases are great but lack the structure needed for Insurance sales Tracking. Alex said he might be working in such a module. I do not want to do the development myself if he is going to do it.

	Eduardo Benaim OP @Reply 3 years ago
Richard Said Not Alex . Sorry

Richard Rost @Reply

3 years ago

To me the differentiation between a family and a company is literally just the name. You could rename the family table organizations and it would work just the same to track family members or company employees. So in that respect I would use the association database table structure. On the other hand in the abcd the main table tracks entities which can be of any type either people families companies you name it. So it really wouldn't matter what you stored in your tables in that case. I built a pretty complicated database for tracking insurance policies back in the late 90s. It's on my To Do List too build another one. I of course appreciate any input.

Eduardo Benaim OP @Reply

3 years ago

Great. I am willing to contribute. In my view there needs to exist PersonsT, FamilyT and BizT (Small Business). every Person has to Belong to a Family (even One Person). Some Families can be grouped under the Biz Table. This is the case of a Small Biz offering insurance to their employees and family members (or Just alone) Please see illustration. I just do not want to alter your Database until it is finished. Maybe you can find it useful for Associations.

	Eduardo Benaim OP @Reply 3 years ago

Richard Rost @Reply

3 years ago

You're probably about the fifth person that is said to me that they want to have company or some kind of other organization in addition to a family membership So what I think would be wise to do would be to simply incorporate all of those into a group table where a group can be either a family a club a company or any other kind of organization. This would involve rebranding the family table as a group table and making it a many to many relationship instead of just a one to many relationship. But I think it would work better for the database and this would be a good example of how sometimes you will come across things like this that make you completely redesign the database midstream and it also illustrates how important it is to get all of this laid out ahead of time because it's much easier to do if you have it in the road map versus changing the database after the fact. But yeah sure since a lot of you asked about this maybe we'll do this in the next video or two.

	Eduardo Benaim OP @Reply 3 years ago
I woke up today prepared to do this. For Me it is a MUST. I am thrilled that you are going to incorporate this in the Main Database. This way I don't have to deviate from you database. BRAVO,,, BRAVOOO, BARVOOOOO!!!!!!

Eduardo Benaim OP @Reply

3 years ago

Richard:
This will be a superb Learning Experience for all of us.
The way I see it every Person can belong to a Family and/or/not to a Company (Group).
Insurance Products are designed for Individuals or Families. The may or may not be grouped by Company.
This year the 'Small Business Health Options Program" (SHOP) will be BIG.
I am gearing up to include Small Businesses (Companies) in my Database.
To Clarify, Health Insurance products (Personal, Family and SHOP) are designed for:
     1. Individuals (Family with One Member)
     2. Families (Family with more than One Member)
     3. Companies (Collection of Families and/or Individuals in a Company)
So it is important to set up the groups from the beginning.
I'm looking to query Companies, Families, and Individuals.
I thought there had to be separate tables for Families and Companies?
Are you are proposing to have Families and Companies in One Table?
Can't wait. Again, thank you for the learning experience.

	Eduardo Benaim OP @Reply 3 years ago
By the way. I remember clearly when you changed Persons to Entities in the ABCD database. It is NOT fun to do with a working mainstream database.

	Richard Rost @Reply 3 years ago
Oh... It's gonna be fun...

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Forum.

Next Unseen

New Feature: Comment Live View