>Try puting in your form.find the following :
>

>cCaption='MyCaption'
>cNewWorkArea='MyNewWorkArea'
>cNewDialogClass='frmPowerFindCustom.scx'
>DODEFAULT(cCaption,cNewWorkArea,cNewDialogClass)
>

>
>You really don't need to pass cNewWorkArea nor cNewDialogClass if you're using the forms properties.

Ivan,

Thanks for the feedback, I'll try it at some point (hopefully today). This brings up another question. I use the form's original find to do things like:

thisform.Find('vPhone', 'fkCust = ' + TRANSFORM(vCustomer.pkCust)

If I implement the PowerFind, I won't be able to do this anymore, right? Couldn't I just do this:

Add a PowerFind() method to my base form
Add an Action for PowerFind
Add a toolbar button linked to the action

Then, I would have both the Find and the PowerFind available. That way, I could use CM's Find() for internal lookups and record navigation jumps and PowerFind() for user searches. Is there anything missing with this approach?