Hi Tom,

First, I must say I am disappointed. I really expected a "Move to Florida" or similar from you :>)

I have two major applications with a similar requirement. One is for Canada and the other California. California and New York are similar in what they tax and other details and yet each is unique. My solution is much like yours as it is easy to maintain by using procedural code, OOP and is table driven. I have an interface for the user to easily modify values. What a pain for the user!

NY only allows changes to rates once a year, so the user isn't pounded too badly with this one. It is the monster CASE statement that I see getting out of hand. Now, if other states get as foolish as NY does in this respect, I am definitely getting that MiniMart job :>)

My suggestion: If it works invest your time in anything else. O.K., so I am lazy! :) Software is never finished. Do you find yourself waking up at 2 AM and saying to yourself, "Gee, that app I delivered 2 years ago - I just thought of a really cool way to do something"! I gave up such thoughts long ago and look to the future and anything that is not concerned with programming! :)

ROFL! Yeah, me lazy too. No, those early morning inspirations usually have something to do with the bathroom in my case. To quote my mom: "The Golden Years? Keep them. I want my copper ones back."