>Personally, Nadya, I find your "need" to "optimize" every piece of code that you come across to be REPUGNANT in the extreme.
>I think it is fine, well and good that you want to review/optimize any code, actually, but it is your penchant to so cavalierly expose anyone ELSE'S code TO THE WORLD, with your silly comments about it, that is sooooo irritatingly GAUCHE (second time to use that word today)!
>
>You've noted in prior messages that your "colleagues" of that time did NOT appreciate your wanting to "help" them 'correct' their poor coding techniques. Why do you think that total strangers would feel any different?????
>
>This has gotten RIDICULOUS and I HOPE THAT YOU WILL STOP DOING THIS IMMEDIATELY.
>
>Jim

Here is an e-mail that I just sent to my colleagues with the subject "New RI - I'm at my wit end":
=====================================================
Hi everybody,

Last few days I was going through the New RI code trying to optimize it. Unfortunately, it seems like my efforts were in vain and this code is still dog slow. I’d like another set of eyes to look into this code before we abandon the idea of using it. It does its job, but for the bulk updates we would need to disable them if we want a good performance.



Here is a thread, which is relevant to this problem. I would appreciate your comments.

Re: SEEK(),INDEXSEEK() or KeyMatch() or SELECT-SQL? Thread #1002645 Message #1002800



Thanks in advance.