Difference between revisions of "Orphaned Blocks"
From WireCAD Online Help
Wirecadadmin (Talk | contribs) |
Wirecadadmin (Talk | contribs) |
||
Line 3: | Line 3: | ||
What is an "orphaned" block, how to the happen and how to I fix them? | What is an "orphaned" block, how to the happen and how to I fix them? | ||
− | Generally speaking, orphans occur when we attempt to lookup information about a block from the database and the information cannot be found. | + | Generally speaking, orphans occur when we attempt to lookup information about a block from the database and the information cannot be found. |
Line 14: | Line 14: | ||
#In the case of a SysName lookup the SysName and Location fields are not found to match. | #In the case of a SysName lookup the SysName and Location fields are not found to match. | ||
− | + | [[File:Orphaned1.png|thumb|Typical Lookup. Everything is working]] | |
Revision as of 16:27, 24 March 2014
General Discussion
What is an "orphaned" block, how to the happen and how to I fix them?
Generally speaking, orphans occur when we attempt to lookup information about a block from the database and the information cannot be found.
This can occur for several reasons:
- The project has been moved without using the Packup/Unpack process.
- The data was deleted from the database.
- Multiple instances of the requested data are found. This can be the result of duplicate entries in the database.
- In the case of a SysName lookup the SysName and Location fields are not found to match.
Orpahned blocks occur when we create custom equpment definitions, use those equipment definitions to create blocks, and subsequently remove the equipment definition from the database.