JohnDanter2
VIP Member
Hi folks
I have a weird one. In PROD, if a user enters scrap in P31116 W31116I and clicks OK it gets saved to F3111 SOCN and I can see it in the next screen, the G.
However in PY UT this is not working and it's only saving to CTS8 (but this an IO statement not a headerless detail type save)
Only difference is P31116 has had BSVW V3111B changed to left outer join to F4108 to show some LOT based fields from the parts list. I then use UDOs to show the extra columns
I have done this type of mod countless times. No code just a BSVW tweak and then use UDOs to add the columns, but these are on W31116G find browse, not the I headerless detail
When I debug, the event Update Grid Rec to DB-Before Form: Component Scrap Revisions - W31116I is getting fired but there is never an SQL to update F3111
Only thing I can think of is W31116I does not like the newly amended V3111B specs somehow and is getting lost in an update?
Thanks
John
I have a weird one. In PROD, if a user enters scrap in P31116 W31116I and clicks OK it gets saved to F3111 SOCN and I can see it in the next screen, the G.
However in PY UT this is not working and it's only saving to CTS8 (but this an IO statement not a headerless detail type save)
Only difference is P31116 has had BSVW V3111B changed to left outer join to F4108 to show some LOT based fields from the parts list. I then use UDOs to show the extra columns
I have done this type of mod countless times. No code just a BSVW tweak and then use UDOs to add the columns, but these are on W31116G find browse, not the I headerless detail
When I debug, the event Update Grid Rec to DB-Before Form: Component Scrap Revisions - W31116I is getting fired but there is never an SQL to update F3111
Only thing I can think of is W31116I does not like the newly amended V3111B specs somehow and is getting lost in an update?
Thanks
John