M
Mike375
Guest
Mile
From your posting:
when a new instance of a class is added to a database (i.e. a new employee) their details fill a database record and not a database field and/or table.
I would love to know how you would add another insurance company as a record or records to the same table
For example, how would you do their rate/quote system?
You appear to be operating under the impression that each one of these is just like another person and only the address, name etc change.
I would also love to know how you would store in one table prospects that are vastly different. Surely you would not be suggesting that all the fields we have for the medical specialist to "indentify" him would also be used for other occupations. Are you suggesting a table that is a mile wide and with heaps of blank fields.
Likewise with the insurance company products. Surely you are not suggesting a table so wide that we can do each insurance company on one table. What do we do with all the blank fields.
How do we store the base insurance rates in one table from the different companies. Holy shit, that table would be very wide. It appears that you are addicted to blank fields. With the general insurance company I guess we would just leave all the fields blank that related to the various policies offered by life insurance companies.
Are you suggesting that with the different life companies we just leave a bunch of blank fields because Company A has products ABC and Company B has ZYX. I guess it would be OK since they share several products that are essentially the same.
Mike
From your posting:
when a new instance of a class is added to a database (i.e. a new employee) their details fill a database record and not a database field and/or table.
I would love to know how you would add another insurance company as a record or records to the same table
For example, how would you do their rate/quote system?
You appear to be operating under the impression that each one of these is just like another person and only the address, name etc change.
I would also love to know how you would store in one table prospects that are vastly different. Surely you would not be suggesting that all the fields we have for the medical specialist to "indentify" him would also be used for other occupations. Are you suggesting a table that is a mile wide and with heaps of blank fields.



Likewise with the insurance company products. Surely you are not suggesting a table so wide that we can do each insurance company on one table. What do we do with all the blank fields.


How do we store the base insurance rates in one table from the different companies. Holy shit, that table would be very wide. It appears that you are addicted to blank fields. With the general insurance company I guess we would just leave all the fields blank that related to the various policies offered by life insurance companies.
Are you suggesting that with the different life companies we just leave a bunch of blank fields because Company A has products ABC and Company B has ZYX. I guess it would be OK since they share several products that are essentially the same.

Mike