>>>>>>On a form, it's easy. How can I search for a text string in a report?
>>>>>
>>>>>What exactly do you mean here - when you preview a report or to find particular field in a report?
>>>>
>>>>In a report form or the frx, I want to find a text string that could be anywhere in the report. In a form I can just open a method, ctrl-F and find whatever I want almost wherever it is. In a report I can't, but I want to.
>>>
>>>Open report as a table and then try browse for 'search string' $ expr
>>
>>Yeah, I know, but it's a shame that the report form isn't more like a regular form.
>
>It is equal to a form.
>On report design you CAN search into the de methods LIKE a regular form.
>On report design you CANNOT search into expressions list LIKE a regular form,
> where you cannot search into the properties window )
>
>Unfortunately a report is not a class ...
>
>Try with "Code References"

I would like to have the same menu for a report form that I get for a screen form. Add props/methods, etc. Only in the DE can you have that. But the search thing is that even if I use code references, it will not open up actually where the string is found, just opens the report. I can do that myself. If I'm trying to find a string somewhere in a report - and I know which report already - there is nothing to tell me where that string is located. Box.Print only when... is not good enough. I could have 10 boxes on the form. Now I have to go to the form and edit every box to find the right one. In a screen form, I can just edit from code references and it will open the actual object. That is the difference to me. Hell, I know I can open a report form and look at all the boxes, but I would like it to work more like a screen form, and it doesn't.