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

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

Recommended Posts

  • 2 weeks later...
Posted

If you are multi-user, I would add one line to that Lock script, something like:

If [not lock] or If [isEmpty(Lock)] or Error Capture 301 immediately following the Set Field to protect against record lock. Because if another User has possession, it will not set the field. crazy.gif

... And then notify User the field did not lock or loop the Set Field [] until you have success. That may be a Management decision ... how important is it at certain phases throughout your scripts? List your restriction needs and then determine your course of action if the lock does not set.

LaRetta

This topic is 7499 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.