>Now I understand what you are trying to do. I have several places where I have a button to "find" a record in a data entry form, for example a contract #. What I do is open the contract form and automatically have the form execute the find button located on it. The contract find form is opened allowing the user to fill out in any information they want to locate the record they want to find. Then the user selects from the grid that is populated in the find form. When they exit the find form the program returns them back to the contract detail form which they can edit or modify how they see fit. When they exit that form then it returns them to the data entry form they were originally in and fills in the contract # they selected.
>
>By doing it this way you don't have to sub-class and change how the find form works but it still allows the users to modify any records before they select it.

Hola Cathi,

Your approach is quite easy to implement. I like that about it, but then it complicates things for the users as they get an extra form floating around on their screen. I'm guessing that you bring up the Contract form and then through a parameter you probably trigger it to self-click its Find button. But then, after they chose their Contract they get back to the edit form, where they have to click OK now, right?

I just want them to click on a find button; if they find the record good, if not, I give them an option to add it and that addition becomes then their selection.

I ended up using the addProperty method and it seems to be working like a charm (well, at least the oRox hasn't been visible lately, which is also good news for me).

Alex