I mention the solution to this in my other post called "A Tale Of Two Slaves"
You mentioned that the problem started happening when you shifted to the Network Suite. So, while Marsha_R suggestions are still valid, I'd look at a couple of other things as well.
ClickTab is executing a specific action on the tab that doesn't require the recognition of screen location where as DoubleClick is doing a screen location. What this seems to indicate to me is that the remote machine executing the network job MIGHT be dealing with screen resolution issues where the object may be dimensioned smaller than on the originating machine. So, while a pixel location on the object of 90,15 may work on the developer box, that might not work on the remote box. If you don't want to have to mess around with changing code around too much, you might want to see what screen resolution, scaling, etc., is implemented on that remote box.
tristaanogre fyi, the link I posted to the double click documentation actually says it's *not* screen coordinates.
True... but let's say that the screen resolution on the remote machine is smaller. So, the object itself is smaller, pixel wise. So 90,15 may be outside of the bounds of the object on the remote machine. It's still worth investigating... the alternative is to remove those co-ordinates from the DblClick method.... always a good practice unless you explicitly need them. But making sure resolutions match would resolve the problem, potentially, throughout the code and not just on that one line.
tristaanogre wrote:
the alternative is to remove those co-ordinates from the DblClick method.... always a good practice unless you explicitly need them.
Which is what I recommended above... :)
