I have a strange problem and I was wondering if anyone else had a similar problem and possibly a solution.

I have a script in "File A" that calls a script in "File B". After the child script in B is fully executed, script A executes the "Exit Application" script step.

The problem is that the filemaker.exe process is left hanging. The user does not know this until they try to open filemaker back up and nothing happens. If you go into the process window from the Task Manager and kill the filemaker.exe, you can go back into filemaker.

After some trial and error, I discovered that the filemaker.exe is not left hanging if I don't call a script in File B.

The purpose of File A is to call an script in File B that updates the database overnight. Once File B is updated, the whole app is closed. My temporary workaround is to just close the files and not exit the application. Not as clean though...

Any thoughts would greatly be appreciated.

How about changing the Exit Application step to be executed in the child script B? I don't see where it would make a difference, but it's certainly worth a try.

Brent,

That's a real good idea. I'll try it and post the results.

Thanks!

I *hate* when developers exit the FMP application when I close a file. Like, they think that their database is the only one I ever use? I'm often running multiple solutions at once. If I close one I don't want the whole program to exit.

At most, cleanly close just your databases including all the little related ones (join files and stuff). But please leave the application running. The user can close it themselves.

It's about as annoying as trying to exit Dreamweaver 4 by closing the last window: you can't. You have to choose Exit from the File menu to get rid of it.

Or add a test

If [ValueCount(DatabaseNames) = 1]

Exit Application

Else

Close [ ]

End If

Brent ... I tried it and it didn't work... thanks anyway. I think that it must be a flaw in software. I tried it on 2 other computers and it does the exact same thing.

Vaughan ... I understand you frustration. However, in this situation, it is strictly an update script on a drone computer, which happens to be mine. There is not going to be anything else running, as I am calling this script in the middle of the night.