Thanks.
This solution would work, but if I Change the RTEX to "heavy hex nut", ISODRAFT will still grab the ID-Number of the bolt, which means I have to create an extra LTAB with imaginary bolts, which have only one length (which will be ignored), which shall be described as nuts and have the RTEX and the ID-Number of the nuts, Point to the SBOL which has only the WASH....
Disadvantage is: I have to take care of material-number for nuts two time: in SPCOM (for "normal" connections) and in DTAB (for nuts which are "stored as" bolts)....
Or maybe I got something wrong.....
I still think, this is a standard case and AVEVA should really deliver a BTYP like FSTUD or so for such a situation ...
Thanks.
This solution would work, but if I Change the RTEX to "heavy hex nut", ISODRAFT will still grab the ID-Number of the bolt, which means I have to create an extra LTAB with imaginary bolts, which have only one length (which will be ignored), which shall be described as nuts and have the RTEX and the ID-Number of the nuts, Point to the SBOL which has only the WASH....
Disadvantage is: I have to take care of material-number for nuts two time: in SPCOM (for "normal" connections) and in DTAB (for nuts which are "stored as" bolts)....
Or maybe I got something wrong.....
I still think, this is a standard case and AVEVA should really deliver a BTYP like FSTUD or so for such a situation ...
