I’m pretty sure I’m overthinking this. I have an UltraGrid on a UD form that will be used to enter defect information about a lot number. There can be multiple defects and each one needs to be it’s own separate row in the grid but each defect needs to directly linked to one specific lot number. In order to accomplish this do I need to use a separate table to store the defect information and link it with a FK? Has anyone done anything similar to this?
Just off the top, I am thinking of a UD table (with child records) with a uBAQ bound to a custom grid. Your key fields would relate the UD record to your lot (so maybe Key1 = Part, Key2 = Lot, or whatever your config is). You’d then have a mechanism to programatically grab data from the UD form to create a new UD record, thus relating the new UD record to your lot.
The initial record would be the UD rec, and the defects would be child records under that so you could have any number of “defects” per UD record.
1 Like
You can either have an increment on Key5 or use UD1##/UD1##A table.
1 Like