Hi Gerry

>>I was not very keen on the solution you mention below since the method would be executed mutiple times even on grids that do not have a .GridDoubleClicked method
>
>Sorry. I don't follow.

Well the event would fire every time a field is double clicked even if I am using a grid where I dont want this behaviour. I know that the event will do nothing its just that I always try to code to avoid any actions taking place that are not required because I end up having to step through them all the time and there is overhead to consider.

But on balance I think you are right in this case. Because you leave the .GridDoubleClicked method on view all the time it serves as a reminder that this functionality is there. Since my way would involve stepping through a PEMSTATUS there is no difference in overhead.

Sigh guess I just hadn't thought it through enough (a habit of mine sometimes)

Thanks for the tip:)



>>Also I have not yet experimented with the builders for implementing grids that make use of my own custom classes. I suspect there may be some problem in that area.
>
>I don't use builders ... all my Grids (several hundred) are all defined using DEFINE CLASS. They all do double-duty in Views, Lookups, and "Multi-Select" Grid picklists.
>
>>Since the amount of labour I am trying to save is fairly small it looks like Nick's ingenious click transparent class will be the quick solution to this problem. I expect I will find more way to use this class as well.
>
>If it works for you, great.