Have you tried having a message box?

@ BigLouie - Yes, message box is showing the message but i'm trying to show a script error that will prevent the user from continuing.

@Kent Mackall - I'm running the script in TTT. We want the message to trigger when a change is made on the Unit Cost on Sales order line item. Regardless of the item valuation, we are trying to prevent a sale when the cost is more than the unit price.

@W Jezewski - I tried oScript.SetError on Pre-Validate event but that didn't work too. 

@ BigLouie - Yes, message box is showing the message but i'm trying to show a script error that will prevent the user from continuing.

@Kent Mackall - I'm running the script in TTT. We want the message to trigger when a change is made on the Unit Cost on Sales order line item. Regardless of the item valuation, we are trying to prevent a sale when the cost is more than the unit price.

@W Jezewski - I tried oScript.SetError on Pre-Validate event but that didn't work too. 

Greetings,

Good point by W Jezewski about oScript.SetError and Pre-Validate.  

Have you put message boxes in the script to test

A) That the script is actually executing

B) That the values of cost and price being set are such that the message will display.

Thanks,

Kent

Kent notice where he says to me that the message box is working but he is trying to stop the user from continuing.  I remember Steve posting a script once that did that.

I did notice that after my response and I was doing some testing on my system.  If the message is displaying in the Pre-Validate as an oScript.SetError then I am not sure why processing would continue.

I am testing on Sage 100 2014 in ABC Demo Data Company using a new inventory item I set up as a standard cost item with a cost of $1000 and a Price of $0. In my testing, the behavior is as expected.  The warning message displays, the Quantity ordered is zero'd out and focus is set back to the Ordered column.

Thanks,

Kent

@ BigLouie,  @Kent Mackall and @W Jezewski.

Thank you so much guys. I don't know why the warning won't pop up either. I have informed the client and they are settling for just the messagebox.

I guess that's good enough for now. Thanks for your prompt responses and efforts.  

tobitimac sometimes the .SetWarning() will not execute because of logic in Sage's validation that may turn off the warning.  Safest play here is to go with the message box that you are already implementing.

E