According to the help page for AccessMode Enumeration in the NI .net help the autoupdate modes are only valid for DSTP and logos sources and targets.
The document “Why Is the "ReadAutoUpdate" Mode For My CNiDataSocket Object in Visual C++ Not Working Correctly When I Access My OPC Server?”, http://digital.ni.com/public.nsf/websearch/a909c952a992ea2086256b61005cb373 states that “The ‘ReadAutoUpdate’ mode of the CNiDataSocket object does not support OPC”.
However, I don’t find any mentioning about not being able to use autoupdate modes when binding ActiveX controls to OPC sources in the document “Connecting Measurement Studio User Interface ActiveX Controls to Remote Data”, http://zone.ni.com/devzone/conceptd.nsf/webmain/bec99c690cc6c4d98625687f00605787, and perhaps more importantly I am currently using autoupdate modes both in managed c++.net and in standard c++ and this seems to be working just fine.
So now I am a bit puzzled. When can I use the autoupdate modes and when can I not? The simple answer is of course that since it seems to be working for me why not use them. However, I would like to be sure that this will not cause any unexpected results, like e.g. loss of data.
I am using Measurement Studio 7.1, if the issue is version dependent.
