They have to close and reopen SO entry to load the script, but yes, it should apply to everyone.

The trigger I recommended runs when you click Totals, not when you click Accept, so you have a chance to change the date before saving.

Sage City has lots of code snippets, so if you need examples, read the forum history.

I've been messing with the code a little bit today to try to get a message box if an order has a ship date older than the current date. I'd like it to pop up whether it's when I am creating an Sales Order or editing one. I don't get an error code but it doesn't give me a pop-up box. I'm not exactly sure what logic is behind "if oSession.UI <> 0" but that is the only thing I would suspect would prevent the message box from popping up. Would this be why? If not, what would be causing it? I've been looking around for something similar on the forums and can't seem to find anything about it. If this is something you wouldn't usually answer that's understandable and I don't expect you to answer it. Any help is appreciated. Thanks.

retVal = 0

sShipDate = ""

retVal = oBusObj.GetValue("ShipExpireDate$", sShipDate)


if oSession.UI <> 0 and sShipDate < Date() then
	
	retVal = oSession.AsObject(oSession.UI).MessageBox("Ship Date is Past Due")

end if

The oSession.UI filter is just to prevent the script from running when there is no UI (like when an order is being updated while posting an invoice batch).

The Sage date format is different than the format for your Date() returns so you are comparing apples to oranges. 

Search these forums for FormatDate and GetFormattedDate to learn more.

Alright thank you for giving me some direction. I appreciate it.