Is there any reason you have to use AddCustomInfo3? The latest version of those API calls are more powerful and allow you to check whether or not the change was successful.
Something along the following lines:
Dim configuration_name as string
Dim CustomPropertyManager as sldworks.CustomPropertyManager
configuration_name = "" 'empty string for non configuration-specific
set CustomPropertyManager = swModel.Extension.CustomPropertyManager(configuration_name)
if CustomPropertyManager.get(arguments) = swCustomInfoGetResult_NotPresent then
Thank you very much John Alexander for your quick answer.
The only reason I am using AddCustomInfo3 is that I am editing an old macro I wrote years ago, and I am too lazy to change to the new ones .
Thanks again for your replay, I think I have to switch to the new method.
(but yet I will wait a while, I may get an answer that helps my laziness ).
I thought you noticed a similar situation as I had, but it seems they are different after all.
I noticed with my SW2017 installation that I couldn't edit the Summary Info (title, description) after it has been added once