Allow User Abort / can I stop all user database activity

[Steven Cappiello]

Hi,

I have a process-heavy database that runs a few local scripts, runs an external script, and then saves up to 6mb of files to a network drive. As it is, I think I can click onto a window and interact with FileMaker at some points as everything is running... how can I lock things down so that a user can do nothing until the scripts, both local to the first database and also the external scripts, are done running?? Is it enough to set "Allow User Abort -Off" on all scripts and subcripts ??