S
Sylvia Knof
Hi all,
I use the TreeView control on many forms with Microsoft Access 2002 and
Microsoft Windows Common Control 5.0 (SP2).
Everything worked fine since a few months ago.
Since then the NodeClick event of all Treeview controls is not fired if the
network cable is plugged in and clicking with the mouse on a node. If I
select with the keyboard everything works fine. On a laptop not plugged into
the network also everything works fine.
In my home office this doesn't happen with devolo Microlink dLan.
Our customer who works with the software also has a network but there the
NodeClick event also works correctly.
But in our office the NodeClick event ist not fired if the network cable
is plugged in. If I remove the cable I must shut down and reboot the system
before the NodeClick event is fired for the mouse. For the keyboard the
NodeClick event is always fired correctly.
We are sure that the NodeClick event wasn't fired correctly after
installation of a security update from Windows. At the laptop of my collegue
the NodeClick event was fired correctly a little bit longer. But then she
also installed the security update and since then the NodeClick event was not
fired correctly at her Laptop, too.
We are not sure if this also could happen at our customer's network, so it
is VERY, VERY important for us to solve this problem.
Thanks for any help,
Sylvia Knof
I use the TreeView control on many forms with Microsoft Access 2002 and
Microsoft Windows Common Control 5.0 (SP2).
Everything worked fine since a few months ago.
Since then the NodeClick event of all Treeview controls is not fired if the
network cable is plugged in and clicking with the mouse on a node. If I
select with the keyboard everything works fine. On a laptop not plugged into
the network also everything works fine.
In my home office this doesn't happen with devolo Microlink dLan.
Our customer who works with the software also has a network but there the
NodeClick event also works correctly.
But in our office the NodeClick event ist not fired if the network cable
is plugged in. If I remove the cable I must shut down and reboot the system
before the NodeClick event is fired for the mouse. For the keyboard the
NodeClick event is always fired correctly.
We are sure that the NodeClick event wasn't fired correctly after
installation of a security update from Windows. At the laptop of my collegue
the NodeClick event was fired correctly a little bit longer. But then she
also installed the security update and since then the NodeClick event was not
fired correctly at her Laptop, too.
We are not sure if this also could happen at our customer's network, so it
is VERY, VERY important for us to solve this problem.
Thanks for any help,
Sylvia Knof