I have a simple subroutine, which worked in Cadiopia IntelliCAD 2001, and simply lists Xref's to an MS Excel worksheet. When run for ProgeCAD 2016 I get all the blocks identified as isXref=false. I know they are Xref's, but they all have bad paths, they are also nested.
The original purpose of the routine was to list the Xref's, so I could mess with the path strings in a worksheet, then generate a Script file (*.scr) to correct the paths. I was hoping to modify the subroutine to fix the paths entirely. though not certain if path is a property of the Block definition or insert. Scanning through entities also only identifies Block inserts, it does not find any External References. Rephrase that: it returns the external references (EntityType=16) as block inserts (EntityType=6).
In ProgeCAD the xref's show up as External references in the properties box.
The computer is 64 bit, with 64 bit windows 7. IntelliCAD 2001 is on a different machine so not there to cause interference.
Anyone else experienced similar? Can someone confirm if this is a flaw in ProgeCAD vba objects?
The original purpose of the routine was to list the Xref's, so I could mess with the path strings in a worksheet, then generate a Script file (*.scr) to correct the paths. I was hoping to modify the subroutine to fix the paths entirely. though not certain if path is a property of the Block definition or insert. Scanning through entities also only identifies Block inserts, it does not find any External References. Rephrase that: it returns the external references (EntityType=16) as block inserts (EntityType=6).
In ProgeCAD the xref's show up as External references in the properties box.
The computer is 64 bit, with 64 bit windows 7. IntelliCAD 2001 is on a different machine so not there to cause interference.
Anyone else experienced similar? Can someone confirm if this is a flaw in ProgeCAD vba objects?