>>The business object ahs a getfielddata method that accepts a field name and returns the field's value. The RefreshData method fo the form or container or whatever does;
>>
>> THIS.Text1.Value = THIS.oBuzObj.GetFieldData("Customer.Name")
>
>>The writeData method of the form et al;
>>
>> THIS.oBusObj.WriteFieldData("Customer.Name",THIS.Text1.Value)
>
>>The form has no tables or views open, mainly because I can't depend that any frontend might be capable of using tables or views, but they can all call a method of the busobj and get the return value back.
>
> Hmm..interesting..are your GetFieldData/WriteFieldDate methods "generic" or do you have to customize them with each new project you do? It looks like they could just be drop in methods. Very interesting. I''m thinking you could also use something like this in those situations when you have a VFP front-end and want to take advantage of the easier VFP to VFP to x situation. Use views/tables where they're easier on the front-end, but expose those methods (GetField/WriteField) so that other "not-yet-thought-of" programs can access the data if they need to.
>
>-Paul

Basically, the business object acts as or calls wrapper-class methods for all database IO, if I am understanding this correctly. It's a very good way of doing generic IO.