>Hi Nadya
>
>I have to say, proceed very carefully!!! Changing the index expressions in a table will likely cause changes in other areas! Changing the query to match the existing indexes would be safer. Don't forget to restart the machine after such a change to ensure the better performance is not caused by caching.
>

Hi Mike,

I agree with you, but yesterday we discovered some really nasty indexes like ALLTRIM(UPPER(c_lName)) with FOR conditions. On Monday we're going to discuss the indexes and database model. We rather do it now than later after lots of programming efforts have been done. In my opinion, the Business Requirements should always come first, then thorough Analysys, then Data Model, then Prototype, then Coding, then Debugging.

Otherwise there is a great risk of never ending changing stuff and re-designing. I am new in the company, so I can not dictate how things should be done, but there definitely should be done lots of careful planning and designing...