>So you would use the oToken.AddProperty to add each property, use the resulting property in the FindForm controls and then, upon return to the calling form, use the same values to populate the edit views?

Exactly. I actually created the token object with a number of propoerties that I know will be used throughout my forms, but if I needed to add a property on the fly I'd use the addproperty method. Yes.

>In that case, if you return a value from the FindForm, you can remove oToken. If you don't return a value, you can add a record and use the property values to populate the view fields and then remove oToken.

You could add a property used for success/failure, populate it accordingly from the findform and then have the calling form act based on its value.

Have fun!

Alex