>>>This still table still has over 60 index tags precisely for this reason. We only removed indexes when we could assert what their impact on the system is. The performance problem was much easier solved by keeping the table open in a private datasession on slow networks.
>>
>>
>>This is the first system I've looked after where I don't necessarily correct faults.
>>
>>Instead I ask.
>>
>>How often do you have this problem ?
>>
>>Is it reproducible ?
>>
>>How much trouble does it cause you. (How much does it cost you) ?
>>
>>Do you have a possible work around without making a change ?
>>
>>Bsed on the answers to those questions I may look at it or ignore it.
>
>Whil Hentzen had a standard opening line when companies brought their troubled apps to his attention.
>
>"What is the pain you are experiencing?"
>
>He quoted them a high enough rate to make about any pain bearable.

You have to be careful about that. I once had a company that wanted me to fix one of their apps and I really didn't want to, nor did I have the time so I quoted a really outrageous amount and they bought off on it. I had to spend the next 3 weeks or so every evening working on that system. I did make a lot of money, but it was money I didn't need at the time. I wanted more time with my daughter back then.