>Hi,
>
>Does the following business object approach seem sound to you?
>
>1) In the start up sequence of app, we instantiate a global business object, and store a reference to it in a global variable (oBiz), or if you prefer in a property of the App object.
>
>2) The valid method of each UI control class calls oBiz.ValidateField(This) in order to determine the result of appliying the business rule and takes appropriate action.

Who's to say that the alias used in the controlsource of the control is the same as the table name? Your interface layer shouldn't have intimate, binding knowledge of the names of backend fields and tables.

Your object is less a business object than a universal validator- business objects are usually domain specific instead of universal, and contain domain specific methods that represent actions that can be performed on the represented entity.