Hi Erik,

I said that clean interfaces make for good components and the cleanest possible way to pass parameters is to limit the number to one. Passing an object is often a cool way to go, and somethimes passing THIS works wonders.

It's true that the receiver needs to access the parameter object's members, but the converse is also true for the alternative: If you don't put the responsibility in the receiver, then it's the clients that need to know the protocols of the receiver and when you change that, usually you need to change the clients too .

This is really a behavior allocation decision, and it should be evaluated on the engineering merits of the particular situation. Note that in VFP6 it's easy to rig a mechanism whereby if the receiver doesn't understand the call, it can delegate it somewhere to something that can. THIS_ACCESS() is ideal for this...

****************

In the VFP6 class browser, to see the HTML source code, rightclick over the view source button.