>>>for sure we don't go about opening databases when they are already open. In fact, we encapsulated that probably 10 years ago, out of general principle.
>>>
>>>That said, what really counts is what takes how much time when. For that we used the modified profiler, and for views, a couple of our own simple recording tools.If it take 500ms longer but runs a total of 10 times in a session, etc. We try (don't always succeed) to be pragmatic about where we spend our time, keeping in mind that better is often the enemy of good.
>>
>>I disagree. Once you reach a certain skill level, there is no excuse for not writing the fastest running code possible.
>
>
>I cannot disagree more. It is absolutely insane to put your energy in creating the fastest code. It is a utter waste of time to put energy into making a routine a few ms faster at the expense of productivity. I know you're obsessed with ultimate performance, but this I did not expect.
>
>If performance is good enough, it is good enough. If there is poor performance at a certain point in your software, yes you can and should address it, but to go into great lengths for premature optimization goes beyond reason.
>
>Walter,

It's not premature optimization when you already know how to write fast code.