> Rather than having a component "class", explicitly subclassed in the > database to contain resistor specific attributes, I would do it similar > to the following: > > 1 "component class" / table, one size fits all. Each has a component ID.
The Component ID is what I list on BOM. > 1 "attribute type class" / table, one size fits all (?) > > An entry might be: > > Attr_id 213 ... Seems to me like we are starting (re)invent an ERP system. _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user