Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Submitted byAnonymouson09-13-201902:30 PM
Status:
Gathering Support
WDBLKNAM in the catalog database
I would like to see either one of two things to allow multiple symbols to point to a subset of catalog items within a family-specific catalog database table during a lookup operation.
1. The WDBLKNAM field in family code tables should support a comma-delimited format. OR
2. The WDBLKNAM field in the family code tables should support windows wildcards in it's values or search (such as "*" or "?" characters within its value).
The WDBLKNAM field is not for the user to mess with as far as I know it is used by the program to store the family code value based on the block name so it can allow the user to filter on.
IMO the whole database structure should be scrapped and rebuilt with relationships and normalized instead of using wild cards and characters to establish many to one relationships. I thought the SQL version was going to accomplish this but instead it just duplicated the access database structure.
It's kind of sad really when you see the SQL based Vault product and this is all we get for electrical.
So, to further clarify my idea here... The idea is to be able to have multiple symbol file names able to map to a certain subset of part numbers (using the WDBLKNAM field in the db).
When I do a lookup on a component with no catalog information, it automatically filters by WDBLKNAM value = symbol file name (see below).
I would like to be able to have symbols named in easily wildcarded formats such as ?PR1?_RLY-PS, ?PR11_RLY-*, etc. all to be able to lookup to the same subset of parts within a wider family in the db. That's where this idea stems from. If the WDBLKNAM field supported multiple values or wildcards, this could be easily accomplished.
