I want to pause/resume a script for a certain number of seconds.

Problem is, the user can just hit enter and the script resumes right away.

I'm sure there's a way to lock this. I tried "allow user abort" OFF and "error capture" ON, and even hide and locked the task pane, but no luck.

Any ideas?

I don't know of a way to prevent Enter from resuming the script, but you could mark the time in a variable, then loop the pause until the clock has advanced the required number of seconds.

There was a emthod I read about recently on the FSA list (forget who wrote it) that used FMP's field-level validation to block navigation. Basically have a field with not empty validation, and only set it with the script after the pause.

I don't know of a way to prevent Enter from resuming the script, but you could mark the time in a variable, then loop the pause until the clock has advanced the required number of seconds.

I tried this at first, with multple pauses, but the faster the user presses the "enter" key the faster they script resumes.

I also tried adding a field with required validation and then teh script sets it to an invalid value before the pause and then back to a valid value after the pause, but no luck. the enter key still resumes the pause in the script.

I know there's a way. I remember also seeing someing in Advisor magazine or on here someplace about this - I just can't find it.

Ok... I came up with my own...

I just retested using "Paus?Resume Scipt" for 1 second, and then made 60 lines of it.

It works.. sort of. It gives the user the illlusion that pressing the Enter key does not go, when actually it can speed the seconds if they press the enter key more than once per second.

If the user doesn't press the enter key, then after 60 seconds, the script resumes.

Not a very elegant solution, but it'll have to do for now. I've been stuck in development for a while now due to this, minor topic.

If anyone has any REAL solutions to this, I'd be curious to know what they are.

I am very much annoyed by your last remark - implying my post does not offer a REAL solution. Nowhere did I mention "multiple pauses". When someone indicates their skill level is Advanced, I tend to short-hand the solution a bit. If you don't understand the method suggested, ask for a clarification before bad-mouthing.

I am very much annoyed by your last remark - implying my post does not offer a REAL solution. Nowhere did I mention "multiple pauses". When someone indicates their skill level is Advanced, I tend to short-hand the solution a bit. If you don't understand the method suggested, ask for a clarification before bad-mouthing.

Gheeesh... sorry, I didn't realize I was bad mouthing. My appologies, really.

Setting the variable and looping through until the exit parameters are met would have worked just as well if not better than the multiple pause steps.

They way I have my solution set up it to have a user log off via a script, then the script logs them on as a no access account, followed by another log in process. This leaves the user in a NoAccess account until they sucessfully log into their own account. The pause in the script was a punishment/deterent for unsucessfully attempting to log in a few times. I decided not to go with the scipt setting a variable to loop and time out out of shear laziness.. I didn't want to bother with adding the access to the "NoAccess" account. Although this would have beeen easy.