Hi -

I have a field called "Search" which is a keyword field.  I find it a nuicance to have to press F10 to get my results so I entered this programming in the Search LE, on element exit.

var success as int

success = @SelectTreeItem("Search Menu!Search Commands!Retrieve New Results (F10)") 

When I exit the field, I simply move to the next layout element.  It occurred to me that perhaps programming doesn't work in search mode; however, I know that my command buttons work. 

Any suggestions?

Erika -

This raises a couple of "points" for me.  Since I use the "Search" element for most searches, I thought I could at least make use of the On Retrieve Spec Open Event by placing the "cursor" in that element.  I was not able to accomplish what I want.  

I tried several programming statement for the On Retrieve Spec Open Event, including:

goto Search 

and when that didn't work

ThrowFocus(Search) 

and when that didn't work

If @mode() = 2 Then goto Search
 

and when that didn't work

If @mode() = 2 Then ThrowFocus(Search) 

Unfortunately, nothing seemed to work, hence my question.

When, precisely are you in a "Retrieve spec (search mode)?  I presumed that when I pressed F7 and went into search mode that's when I would be in the On Retreive Spec Open event.  I would appreciate help if what I want is "doable."

Since there are at least these two events that can execute programming in Search Mode - and since I think it would be very helpful to execute other programming in search mode - I have a suggestion for a product enhancement and that is to provide for programming in search mode.

Quote:

In this case, why couldn't the "reverse" occur.  Allow programming in Search Mode but only if it is prefaced with either a special "symbol" or:

If @mode() = 2 Then ... etc. 

I think this would be a great feature.  Thanks!

I just discovered a flaw with part of my previous post:

If you go with the @Macro() technique, the "b" (mouse click) version may be the best. Because if you are in update mode and press F7 to get back to the retreive spec, a "tab" macro will advance you to the next element. Plus, if you again press F7 after getting to the retreive spec, the cursor ends up in the record number indicator at the top of the Sesame window.

Spencer,

When I use the code from my last post in this thread, the 'Universal Search' box opens, and I start typing - no need to use the mouse to put the cursor there - works great.

I have noticed that the cursor does NOT blink in the Universal Search box, even though I have the "-blink" startup switch in my shortcut. (The cursor does blink correctly in the form.)

Have you tried typing without first clicking in the box with the mouse?

If it still does not work for you, you could probably use a macro to record 1 mouse click in the search box, and place @Macro just after the command that opens the search box.

I'm not sure I understand. Do you want the Universal Search box to open as soon as you load the application?

I would try the macro method I mentioned earlier.

Let me know if you need more details.

Spencer,

Well, I was going to tell you to use Shift-F2 to start and stop recording the macro. But I just tested it, and Sesame will not respond to Shift-F2 while the Universal Search box is open.  ???

I wonder why I can simply type when the Universal Search box opens, but you cannot.

Do you have the @SelectTreeItem("Search Menu!Search Commands!Universal Search") command in the "On Retrieve Spec Open" event?

Do you have any Goto or Throwfocus commands in the same event?

FINALLY!

Thanks to your "suggestions" Carl --- and trying to reason everything out from our dialogue --- I figured out the problem.

What I was missing was proramming in the Application Manager.  When I added this programming to the "on application open" event, it works perfectly - WITH the cursor where it belongs.

var success as Int
success = @SelectTreeItem("Middle Villagers!Forms!Search/Update!Main!Middle Villagers")  

Now, I is happy and thank you for all your efforts.