Thank you for your comments, Zahid.

>Except for #5, I don't think this approach truly relies on VFP cursors. It seems like it would work as well if the business rules table were in DB2, etc.

I mean using cursors for work instead of recordsets. Passing them in one format or another is a different issue and depends on the receiver.

>With your modification (only instantiating oBiz when necessary), and perhaps the use of MTS, Alex could set this up so that instances of oBiz are not truly created each time they're needed, and are instead just hibernating until something in the UI requests them.

Sounds good for later. For now I am concerned with using a sound approach that would allow things like you say in the future.

>Also, I think you're right, that in a multi-tier system you'd want to pass THIS.ControlSource instead of THIS ... I don't know if COM can handle passing an object reference up the chain, but even if it can, it doesn't sound like good modular design. So I think you'd have to pass two parameters: THIS.ControlSource and THIS.Value.

I think in the case I described passing This is OK because the sender is the screen object and the receiver is the business object (both VFP). But what happens when the front end is Excel? Maybe I need three parameters: cursor, field and value. Comments please.

Alex