>>You really should do it this way. The data is held in the ADO recordset. When you click the Save button, the RS is sent off to the Biz.Validate(). If the data is valid, it calls Biz.Save(), which calls the appropriate methods in the data services. If the validation fails, the appropriate error message is returned for display in the UI.
>
>Craig,
>
>When you have a chance can you look at "Stateless Objects." Thread #416469 Message #416469. I was talking with Evan about the above and would like your input.

Sure. I'll look at it.

>
>>As for Mike's suggestion, when you change the Biz rules, you still have to compile the application, thus causing the compiled code to change in the UI. You still have to redistribute the UI. Lots of value is added to n-tier by using COM and installing biz and data services on an application server.
>
>What is the preferred way for desktop apps? I was thinking about having a ui.dll (has to be a dll for this particular app) a biz.dll and data.dll.

UI.DLL?? You don't get any display from a VFP DLL. A biz.dll and data.dll will work if that's your design.