"Exit Script" have you noticed that...

[Paolo]

If you exit a script via the "Exit Script" step, FM show up the file the script belongs to, even if the window was hidden.

For example:

Toggle Window[Hide]

Exit Script

the window comes out.

Halt script does the same.

Just wondering if it is a bug or a feature...

BTW: it is annoying for me because I often call external script on "data only" databases from the "interface file". If the ext. script exits via Exit Script, the "data only" file comes out.

[andygaunt]

When you run scripts that call external scripts, make sure that the script does not end in that external file, otherwise as you have found out that database will come to the foreground.

Instead, place your exit script in the database that you wish to end in, which in your case would be your interface file.

So, from your interface file

#Your script here

Perform Script [External, data.fp5, "Your external script"]

Exit Script

In your external script the last step is Toggle Window [hide]

HTH

[Anatoli]

I have in all databases script DUMMY, which is called from any other file if I want to transfer focus to file. It is ending with HALT so it stays on that file.

[Paolo]

So the answer is "Yes. We have noticed!"

I think it's bad. I have to exit each ext. script from the end instead of anywhere. This means a lot of nested IFs...

[Anatoli]

I don't get it.

If you start script in file A and then you call script in B where everything stops, why it shouldn't show the file, where it was stopped?

If you use Exit in file B and then calling script in file A will have more script steps, then file B will stay behind.

IMHO it's quite logical.

[Paolo]

It's logical for Halt Script. Because stops the script execution.

It's less logical for Exit Script. Because execution goes back to the calling script. But it's just an opinion...

[Anatoli]

OK, do you have some script steps in file A in calling script after Exit Script in file B?

[Paolo]

Off course no.

But control [should] go back to calling script even if there are no more script steps to execute.

In fact FM documentation says about exit script step:

"Forces sub-scripts or external scripts to stop immediately and return to main script.

"

"RETURN TO MAIN SCRIPT"

But I repeat, it's just an opinion.

...and it doesn't matter that much, since we can't change things

[andygaunt]

yes...but if there are no other lines of the script AFTER you perform the external script the only place it can go is to stop with that database being the last one accessed by ANYthing FileMaker related.

This of course makes that database come to the front.

[Anatoli]

Yup...

[DonH]

Paolo, I understand what you are saying and see the problem. But you are right, you just have to work around this bug ... ooops super nice feature. We KNOW FM doesn't have any bugs.

I think what you are saying tho is lost here. What the problem is is that you want the db with the external script to stay HIDDEN. That doesn't happen even tho the documentation says it should.

And yes, it will take a bunch more "if" statements to handle this problem.

For everyone else, let me give you an example. Say I have a script that needs to pull data from an external db after doing a find on that db. So I execute the external db script and either the data is found or it isn't. If it is, I want to continue with say an export or maybe the calling db takes it and manipulates it. BUT if there is no data returned, I just want it to stop and wait to be called again. LOGICALLY I should be able to just EXIT the script and the calling db takes control again. The documentation says this will happen. But it doesn't. Instead the db with the external script in it pops up to full screen, which I don't want because it now has control.

So the solution is to add in an "IF" statement so that IF nothing is returned THEN something is done on the calling db so control returns to it.

[Vaughan]

No need for heaps of nested Ifs, just put a something at the end of the calling script. A Refresh Window [] step wotks well as does Exit Script. But the main script needs something else to process after the external script.

[Anatoli]

What can be simpler, than to put single script step in?

[Paolo]

Yes, the best option is to put a Refresh Window or Go to Field[] at the end of the main script.

[Anatoli]

Sure