Try adding a standard field in your grid, after the UDF Field.  Like move the "Unit of Measure" up to the primary grid, or the "Description" field, up to the primary grid.  Here is a post about something "similar".  
www.sagecity.com/.../v4-4-the-cost-code-is-required-the-cost-type-is-required----when-entering-a-purchase-order-line

Thanks for the reply, I tried that while on the phone with Sage and it didn't work. I also just tried it again to make sure. Still no luck :(

I have verified with Sage how this happens and duplicated this with them remoted in so they could see it. There is no custom scripting or enhancements, this is all NATIVE Sage 100 code and they will still not do anything about it. I have also confirmed that this happens on different versions so this appears to have been in the code for sometime. Frustrating to say the least especialy given this client cannot use the estimating feature without these UDF's.

I have verified with Sage how this happens and duplicated this with them remoted in so they could see it. There is no custom scripting or enhancements, this is all NATIVE Sage 100 code and they will still not do anything about it. I have also confirmed that this happens on different versions so this appears to have been in the code for sometime. Frustrating to say the least especialy given this client cannot use the estimating feature without these UDF's.

Have you tried dragging the UDF's to the lower grid to see if that helps?

@Prestnow

Couple of questions:

* Do these UDF's have any other attributes?  Like Required fields or have any default values?

* Does this error message only occur when editing the last row?

Just want to double check the steps to duplicate this.

1. Enter estimate lines including values in the RoomName field as new lines.  (Sounds like you are able to add values when adding new lines, right?)

2. After entering a room name value, go back to a line and change the room name (then you get the error message?)

I have been trying this here and the only way I get the error messages is if I add values to the UDF's on the blank row (which indeed does have all those fields missing).  I think this is what is occurring, that it thinks it's on the blank row with no values.

I've seen line scripts where the detail object and the UI / data entry grid get out of synch (if the script doesn't SetKey back to the original line).

This is exactly what happens, it only happens on the last row. I have a worked around where I am having them import data from an csv file with a VI job to import all of the detail rows. Once these rows are imported they can make changes to rows if needed, appears to only be with new rows. Not a great solution but its doable, still disappointed in Sage's not taking more ownership in their program logic. Thanks for everyones help on this!!