Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 8706 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

Is there any way to stop a startup script that has "Allow User Abort" turn OFF? (I know...why did I turn that off during development?!!) I've gotten myself into a loop that won't let me get into scriptmaker and change my mistake!! I have a backup file but I spent several hours making some serious changes and don't want to start from scratch again.

  • Newbies
Posted

I found the solution in a post from December in Scriptmaker! Looks like I wasn't the only one that has done this. However, let me add something: I created a new db but had to give it the SAME PASSWORD that is normally used for the module I couldn't get into. THEN I created a relationship between the two files and VOILA! scriptmaker was active again. I turned the startup script off and will keep the "Allow User Abort" out of my scripts until I know they work. Thanks for the tip, though. I was about to panic.

Posted

No big deal, but it's proved to be a good habit:

I start all relevant scripts with a short conditional: if current modifier key isn't 8 allow user abort off. And I always hold down the "alt" key when launching scripts.

The advantage is you can leave it in the final version. The client won't know.

This topic is 8706 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.