Hello.

This issue should now be fixed - QuickOPC 2019.2, (5.56.)1055.1 or later. Please download the latest version form our Web site, verify the build number (on the first page of the installation wizard), install, rebuild and retest.

Best regards

Thank you. I now realized we have probably intentionally disabled it by configuration, as there were some disorganized users who could completely mess up the history and "flow" of the discussion by going back and making edits that changed thing A to thing B - instead of using the Edit for simple corrections that have no influence on the substance.

Thank you, I edited it now. On my side, I have an Action button below the post, and it has an Edit command in it. But I do not know how it looks to the regular user.

Please create a separate forum thread for the second, unrelated issue, and then edit your original post to remove the parts that do not relate to the original issue.
Thank you.

Hello.

I was able to reproduce the problem. This appears to be a bug in QuickOPC 2019.2. Thank you for reporting it.
There will be a fix (a new build). Please be patient - it may take some days. I will make another post here when it is ready.

Note that the problem has to do with reading values of type ExpandedNodeId that contain non-zero server index. QuickOPC does not support them, so you won't be able to read that node after the fix anyway. The proper behavior is that a non-null .Exception appears in the corresponding element of the array returned from ReadMultiple or ReadMultipleValues.

Regards