Gary:
Thanks for the clarification.
Concerning your last statement:
>>If it helps, I can tell you that whilst the dynamic WHERE clause sounds
>>good, in practice, I have never found much of a use for it where you have
>>a well designed database.

Perhaps my DB design needs some refinement, but it seems to me in a situation where i have a table like this:

iClientId - Integer - primary key
cClientNumber - Char. candidate key

Where internally the relations are based in the iClientId but in the UI the user will enter a cClientNumber I will either need one view with a complex parameter based where clause (eg. Where between( iClientId, ?iLowValue, ?iHighValue ) and between( cClientNumber, ?cLowValue, ?cHighValue )
or 2 views one based on each of the keys. My hope is that I wouldn't need to create a number of local views but could instead create one view with a changeable where clause. And thus I could create just one Cursor class to represent each of the situations, which I guess I can still do by changing the local view at runtime. I'm intrigued by your statement above, perhaps you could elaborate.

Mike

p.s. I sent you a private email, have you received it?