How many UDFs are we talking about? Why not just add to the secondary grid?

Hmmm maybe 7 or so. I could put them down in the secondary grid but my thought was if I could do a button and a panel then I could conditionally launch the screen with an invoke button script - much like how a tier distribution screen appears or the extended description.

These UDFs are only applicable to certain items. Now if I had v2015 I could conditionally disable the fields in the grid but I sort of just preferred a separate screen. That way these optional UDFs would be out of the way.

I'm thinking about possibly just doing something with option bills... possibly. Though with this client I am not sure if they could really manage option bills themselves going forward. Sadly.

Hmmm maybe 7 or so. I could put them down in the secondary grid but my thought was if I could do a button and a panel then I could conditionally launch the screen with an invoke button script - much like how a tier distribution screen appears or the extended description.

These UDFs are only applicable to certain items. Now if I had v2015 I could conditionally disable the fields in the grid but I sort of just preferred a separate screen. That way these optional UDFs would be out of the way.

I'm thinking about possibly just doing something with option bills... possibly. Though with this client I am not sure if they could really manage option bills themselves going forward. Sadly.

I wonder if you could put the UDFs on the blank space to the right of the secondary grid. Do you think they would change as you scrolled down the list?  

Messagebox can pop up a window and display information.   Example:

retval = oSession.AsObject(oSession.UI).Messagebox( "",  "You info to display here - you can also put variables here")

I do this all the time in scripts.   It's even possible to put custom buttons in to signal different choices in how the script should execute after you click  a button.