Nicholas

There is another choice - and that would be to uncheck "Perform Sub-Scripts" - don't know why you would want this but it is a possibility.  EVERY script that calls another must have "Perform Sub-Scripts" enabled in the call to it.
So, is your issue that the other scripts do fire but don't do what you want or that they do not fire at all?

I just took a look at one of more complex routines in FMP 5.5.

File "A" Script "A" calls File "A" Script "B".
File "A" Script "B" calls File "B" Script "A".
File "B" Script "A" calls File "B" Script "B" which exports text file.
File "B" Script "B" calls File "C" Script "A" which imports text file.
File "C" Script "A" calls File "C" Script "B".
File "C" Script "B" calls File "C" Script "C".
File "C" Script "C" calls File "C" Script "D" which exports text file.
File "A" Script "A" imports text file.
Done.

Other possibilities could be errant Halt Scripts or Exit Scripts.

Stephen

----------

Demonstrating for clients is the best debugging method.

On May 25, 2010, at 2:58 PM, Nicholas Geti wrote:

> Yes. There is no other choice. As soon as one specifies another db, then the option is enabled. This also must be so because Performing the small script does indeed fire in the other db.
> 
> ----- Original Message ----- From: "Cornelius Walker" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Tuesday, May 25, 2010 1:58 PM
> Subject: Re: Subscript calling depth
> 
> 
>> On May 25, 2010, at 1:03 PM, Nicholas Geti wrote:
>> 
>>> Not exactly. The small subscripts are in the same file as the master script and called from it. But if the small script calls subscript in another file, then the subscript in that other file is never executed. It is totally ignored.
>> 
>> Did you ensure the "Perform Sub-scripts" option was enabled in all scripts involved?
>> 
>> Cheers,
>> -corn
>> 
>> 
>> Cornelius Walker
>> The Proof Group
>> http://proofgroup.com/