Thank you for your suggestions.

>Seconding Craigs worries about what functionality to put into which layer - esp. after the thread of firing a table lookup out of a control refresh.
>Those tiny shortcuts add up over time - if you really think about selling your SW you should clean such things up instead of adding more small warts -
>even if often the "correct" architecture will add more code / slowness to the app then doing it dirty.
>Build stable and refactor / optimize a layer begins to eat into the performance ;-))
>
>>Good question. Currently it is a business rule and VFP app does it nicely. I also have a ASP.NET web forms application that needs to do the same thing. And I have a native iOS application that needs to do the same thing. So I was thinking of "moving" this routine to the DB.
>>
>>>Sounds like a business rule. Is the database the correct place for this?
>>>
>>>
>>>>Hi,
>>>>
>>>>Is it possible to set some kind of a 'trigger' that SQL server would send an email when a certain field(s) changes value? Currently this feature is done in the VFP 9 application. I am thinking of how to "move" this procedure from the VFP program to the SQL. Of course, if this is possible.
>>>>TIA