Here is the scenario that I need some input on:

A user enters the quantity of widgets that they produced.  They hit the save button.  The production data is stored in table separate from the widget table.  Once the user clicks save, I want the BO to update the On Hand total of the widget in the widget table.  I am thinking that I would place some code in the AfterSave() method to make this happen.  Here's the rub...what if the user entered the wrong quantity (not that this ever happens--I am just doing some just-in-case type of analysis here  ?  The user finds their production data entry and clicks edit, then proceeds to change the quantity and clicks save.  Now, what is the best way of handling this in order to update the widget table with the difference in quantity?

I have some ideas from previous non-SF days, but is there a good SF way to do this?

Thanks,
Bill 

Thanks for the tips, Trent.  Can you explain how you handle the date constraint?  Not sure what you mean by your statement above.  Sorry for my density.

Bill

It is just a matter of you create a UDF that doesn't perform a query, it would just test on the date and return a true or false.  This way the sorting of the date is not part of the query...your UDF is just called and determines if the record will be included or not. 

Couple of things...first, the checking of the date via UDF doubled the time involved in the query (I am likely not doing it right).  Second, I do not see a way to view the stats generated on the actual UDF used in my query.  Perhaps there is a bottleneck in there, but I am not seeing it.

I will keep tweaking my UDF.  Somehow, this thing should generate results in under 3 seconds.  I can do it manually; however, I need to do this with UDFs.

Thanks!
Bill