Difference between revisions of "Orphaned Blocks"
From WireCAD Online Help
Wirecadadmin (Talk | contribs) |
Wirecadadmin (Talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{unfinished}} | ||
| + | |||
General Discussion | General Discussion | ||
| Line 16: | Line 18: | ||
[[File:Orphaned1.png|Typical Lookup. Normal.]] | [[File:Orphaned1.png|Typical Lookup. Normal.]] | ||
| − | + | [[File:Orphaned2.png|frame|Orphaned2.png]] | |
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. | 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. | ||
Latest revision as of 16:32, 24 March 2014
| THIS PAGE IS INCOMPLETE PLEASE ADD IMAGES AND SUPPORTING TEXT |
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.
Orphaned2.png
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.
