When you assign a script to a button you get the option of having it so that it exits the current script.

However if you have these setup on shortcut keys what command can you add in to the script to make it exit the current script?

Thanks

Simon

Hi Simon,

Take a look at the Exit Script script step and see if that is what you mean.

Lee

Hello Simon, Hello Lee,

The Exit script step terminates the currently running script (the one in which the step occurs) but does not affect any previously launched scripts.

If a script is already running (not paused) when you launch a script using a keyboard shortcut, thye new script will be queued and will commence its run when the currently running script has concluded. Only buttons may be used to *interrupt* a script during its run.

The problem is that I have 2 searching layouts (on 2 different related files). And if you hotkey to 1 and then hotkey to the other it leaves the original still in Find and once you perform the find on one of them it leaves the other in limbo. Is there anyway to get round exiting a find...without a button??

I was thinking of having single search screen but the problem is that how will I be able to tell it to go to different files depending on which field is searched. For example searching for a company (if the "single" search layout is left in the company file) will simply direct to the same file but a different layout BUT if you search for a contact related field how can I tell it this and to go to the a layout in the related file.

(Bear in mind i want to do this all with out the mouse. CTRL + 1 currently goes to find (which is paused) and once enter is pressed the script contines to the layout)

Any suggestions would be great!

Hi Simon,

One solution would be to call an external sub-script near the end of each find script, which puts the other file into browse mode (followed by a Refresh window [bring to Front] to ensure that the script still 'lands' in the correct file).

I've tried setting up a simple script to run when I am in the find mode. Which basically enters browse mode then runs a script which goes to a certain layout in the other file but the front layout that has the find in locks in front with the continue/cancel script showing.

any idea?

I've kind of found away round it by closing the file with the locked find routine running- which isn't ideal as it does make searching a little longer as it has to reopen the file....hmmmm

Simon

Your setup sounds overly complex to me.

How about a separate file with a combined layout drawing from both files?

You should be able to deduce what a user is looking for.

simoncpage said:

...but the front layout that has the find in locks in front with the continue/cancel script showing.

any idea?

If the continue and cancel buttons are still showing in the Status Area, that signifies that the script in that file is in a paused state and has not completed its run. To correct this you will need to identify where the step that is pausing the script is located and either remove it or modify it so that it does not lock the file in front when you want the user to be in the other file.

If you attempt to address the pause but find you are still having trouble sorting it out, I suggest that you post your scripts here so that folks can have a look at them and discuss the issues and alternatives with you. Without seeing the scripts it's difficult to offer more specific advice.