Alex,

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?

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.

Might work, thanks

Rex


>>All,
>>
>>I am looking for suggestions as to how I could take search criteria from a FindForm and use it to populate a newly added record in my edit form. I was thinking of creating criteria views to collect search criteria in the FindForm and using the fields to populate the edit views.
>
>Hi Rex,
>
>I just overhauled a big chunk of an app because the number of parameters passed from form to form was growing beyond what I would deem acceptable (not the same as you, but pretty simmilar... keep reading).
>
>I ended up creating a "token" object (based on the Line class for lightness).
>
>Instead of passing parameters around, I'm assigning the values I used to pass to properties in this object and every form in the system takes or modifies only what it's supposed to.
>
>Do you like this idea?
>
>Alex