>>>>Do you not allozw your buziness class to share (give access to) cursors with clases of other tiers?
>>>>
>>>>Marc
>>>Marc,
>>>
>>>No I don't, because I want a true N-Tier design. Meaning that the business object should be usable by VFP, Excel, VB, Delphi, C++, etc. When ADO is better integrated with VFP then I would consider using that to pass cursors around.
>>
>> So then what (for instance) would you set your ControlSource to in a control?
>>
>>-Paul
>Paul,
>
>In using a business object I don't set the control source. I have a container that holds the controls. The container has a refreshData method that I call. The RefrehsData mehtod gets data from the business object and assigns it to the value of the controls. There is also a writedata method that does the opposite, sends data to teh business object. Only the business object retrieves or writes any data form or to the backend. This is what allows that object to be used universally with other front end applications.

Interesting. I've been meaning to impliment this type of design for testing and such. What type of performance do you get with this type of setup? Additionally, I can forsee some problems that would probably occur, especially with grids.

Something someone mentioned in this thread that I agree with 100%: If you can create your business objects as an OLE server and access them via ole clients (e.g. excel) then you have a true n-tier design.