Mike375

[Rich]

I'd rather subject my nipples to hot tar..

that's as perverted as having 2000 Macros

 

[Mike375]

Mile-O-Phile

Anyone who makes these rate calculators would all prefer to run them from a single table if they could overcome the rate changes from a company.

Is there an easy way that you can deal with this situation bearing in mind that we want to put their rates straight into the system. Typing out the rates is just not an option as there are far too many of them.

Company A supplies base rates in the following format:

age........
30..........Male Non Smoker........rate.......rate......rate...and on
30..........Male Smoker..............rate.......rate......rate...and on
30..........Female Non Smoker.....rate.......rate......rate...and on
30..........Female Smoker...........rate.......rate......rate...and on


Company B

age....
30........Male Non S........Male S.......Female Non S.....Female S

I currently do the rates with DLookup for a SetValue expression and which action line runs depends on what was selected on the form such as age, ocupation class, aiting period, benefit period, policy type and so on. Then the rest of the macro does the discounts for amount of benefit and then the mode of payment conversion.

Mike

 

[Mike375]

2. Modify your application every time you get a new provider

Pat,

Yes, that is correct. I will probably be adding one in a month or so and I basically make copies of an existing rate calculator and then make changes to the field name references etc. as well as the various "conditions" for apply a rate formula.

I'm guessing that each individual schedule has 2 or more dimensions and if you normalized each schedule individually, you would see how they could have all been stored in the same set of hierarchial tables.

I am not sure what you mean by 2 or more dimensions. Is one dimension fields across the page and a second dimension is rows. If so, then that is the case for the base rates. There is usually a minimum of two tables with one table being for Disability or Income Replacement insurance and the other for term life, total and permanent disability and trauma insurance. There are then other tables for occupation classifications and the various premimium loadings for the different occupations as well as those for sports and pastimes. There is also usually a table for the various medical and financial requirements that apply to the various levels of benefits.

The rate tables typically have a number of records from either 21 to age 60 and one record for each age or they are like the illustration I did where there will be several records for each age.

They are a fairly big deal to make as businesses in Australia that do all the rates for the different companies employ several computer people and that is all they do. I don't do all the rates, only those for the policies our business is most likely to be writing. For the odd occassion when something comes that I do not do then we just use the insurance company's quote system. To all of them I would have to move from the insurance business to the computer business

Mike

 

[Kodo]

that's as perverted as having 2000 Macros

yes, but I'm well aware that the tar is, infact, hot and can cause damage to my skin such that it may require grafting.

 

[bjackson]

Mike375
I tried to be polite in the my last post with you,but fair dinkum, you will give us Aussies a bad name.Instead of taking up the time of the many experts(And they are experts) in this forum,why not bundle up your program and make a fortune by selling such an excellent product worldwide.You could probably make enough money to then sack everbody here who donates their time and expertise trying to help people.They help im sure,because it gives them a buzz knowing they have helped,but it must give them the S**** being constanly argued with about F***all.

Bjackson

 

[Mrs.Meeker]

Reading this has made me realize that I have not sufficiently thanked ALL OF YOU who have helped me. When I first started learning Access (and I know I still have a loooonnnngggg way to go, Pat Hartman told me to read about normalization. She said I was treating Access like Excel and SHE WAS SO RIGHT! Being a big Excel user for years caused a slight brain blockage (that and my left handed affliction - supposed to make me creative - seems to make me slow

Anyway, I'm glad I'm not a hardheaded old coot who doesn't want to listen, but argue and look like an idiot.

I'm glad you are all out there helping people like me who want to learn and I'm sorry that there are others who can be so unpleasant. Of course you gotta LAUGH!!!

Thanks again ya'll.
Yeah, I lived in Texas for a spell!
Rhonda

 

[KenHigg]

Ms. Hartman

 

[Mrs.Meeker]

Blush

I was just informed of my error in another post. When I embarrass myself I do it up right!

sorry again!