>>I've done the 'bomb' thing before, but what it did was just disable our software. Here's a good example - we had some software that did auto-insurance pricing - people leased the software and we went updates out every couple of weeks (rates change a lot).
>
>Thanks Victor.
>I'm sure you've thought about this and you have a good reason, but I'have to ask. Why not let the client change the rate anytime they want w/o you having to update them?
>I think I know the answer, but let me hear it..... ;)

Well it's not as simple as you'd think. It isn't just once insurance company - the application is for the agents - and these agents can sell auto insurance from 100 different insruance companies - so all of the guidelines, rate's and factors - underwriting rules, etc for each of these have to be updated. Plus some if it can't be table driven because it's so specific. Its really a huge task - enough to keep 3 full time developers and 6 full time testers busy.