Are you looping through lines at all?  If so, you can throw the UI out of synch with the business object... where a grid refresh helps.  Here are my notes on how to deal with this... originally suggested by Alnoor.

Are you looping through lines at all?  If so, you can throw the UI out of synch with the business object... where a grid refresh helps.  Here are my notes on how to deal with this... originally suggested by Alnoor.

Kevin M No loops, just that single statement. It's the ENTIRE script. I purposefully isolated the screen corruption it to as small a script as possible. I did try the grid update trick, but it didn't help.

Perhaps try InvokeChange instead?  I'm not sure on the syntax for a grid value, but I think someone posted an example somewhere...

If CBool(oScript.UIObj) Then ' use invoke change so the UI is refreshed properly
	Set myUIObj = oSession.AsObject(oScript.UIObj)
	'retVal = oSession.AsObject(oSession.UI).MessageBox("Setting freight amount through InvokeChange")
	retVal = myUIObj.InvokeChange("FreightAmt", nManualFreight)
	Set myUIObj = Nothing
else ' otherwise just set the value
	retVal = oBusObj.SetValue("FreightAmt",nManualFreight)
End If

Kevin M Thanks again. I also tried this for the field (ItemCode) that experiences the corruption without success. By my isolating this to an easy to recreate issue across multiple current versions I had hopes that either jepritch or Natasha Chang would comment or forward to engineering.