Thx Matt.
I got the refnum. But it did not solve my problem anyway.
You told to use the shift register of a global/local variable, but when I do
that, windows will throw two exceptions at address 0 when I exit the
application. Labview will not show the exception until it is closed. Then the
same thing happens. Two exceptions thrown by windows without any information in
them.
This always happens if I call a VI which contains this ActiveX ListView twice.
Therefore I tried to handle three different cases: "Open", "Close", and
"Update". The ActiveX is now only in the "Open" case. But to update the
listview I need the reference in the "Update" case, too. Using any variable
(global or local) or a while loop with just one iteration to get use of the
shift register the same windows exceptions occur. I thought I will get rid of
this by using the components[]->activexContainer->ListView, but its all the
same. If I use the listView reference in two different calls of the VI the
exceptions occur. but the listview is there. it is not destroyed. because the
callback methods handle the events of the listview and update the right component.
I cannot find the answer but it seems that the reference to the activex is 0
and windows tries to destroy it but cannot because the reference is invalid.
Thx,
Alex.
