Great, thank you for pointing that out.
Thanks,
Sam
--
_______________________________
Sam Santiago
(e-mail address removed)
http://www.SoftiTechture.com
_______________________________
Also note that there are two unique IDs for a master. There is the Unique ID, which is constant for a master but gets regenerated if the master is modified. There is also the Base ID, which is constant for the master and all derivative changes involving the master.
--
Mark Nelson
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Thanks for replying. I found this little tidbit of information in the Visio SDK documentation that answers the question:
If a shape, page, master, or style is deleted, future objects in the same scope may be assigned the same ID. Therefore, persisting shape or style IDs in separate data stores is generally not as sound as persisting unique IDs using the UniqueID property.
Thanks,
Sam
--
_______________________________
Sam Santiago
(e-mail address removed)
http://www.SoftiTechture.com
_______________________________
Some ideas: give the masters UniqueIDs (guids) or use the NameU property. Both are available through the automation model - check in the Developer's Help.
--
Hope this helps,
Chris Roth
Visio MVP
Does anyone know why Visio changes the Master ID for each master shape when you save a stencil in XML (as a .VSX file)? I have a DB driven feature with Visio that uses the Master ID to identify shapes, but when a stencil is saved as a .VSX all the Master IDs are different. Any guidance greatly appreciated.
Thanks,
Sam
--
_______________________________
Sam Santiago
(e-mail address removed)
http://www.SoftiTechture.com
_______________________________
