Tom R. Posted November 7, 2015 Share Posted November 7, 2015 I am trying to come up with a way to keep multiple users from working with the same record. I have a main table of leases, and for each lease a user needs to create (or link an existing) record in an orders table. All of the data entry on the lease layout is done using global fields - user enters the order data in the globals, then a script trigger fires a script that either finds a matching order or creates a new one, then creates a link record in a join table. After a lease is processed, a flag is set in the lease record as "completed". Then a script takes the user to the next record that is not flagged as "completed". I'm aware of checking for error 301, to see if a record is locked. But if the user is just viewing the record (not editing a field's contents), I don't think that error will occur - and I'm guessing that if the user is in a global field, the record will not be locked? At any rate, I would just like to make sure that multiple users aren't taken to the same non-"completed" record at the same time. Any advice appreciated. Thanks! Link to comment Share on other sites More sharing options...
comment Posted November 7, 2015 Share Posted November 7, 2015 (edited) 39 minutes ago, Tom R. said: I am trying to come up with a way to keep multiple users from working with the same record. Filemaker already does this for you by locking a record as soon as one of the users begins editing it. There's no need for you to do anything. 39 minutes ago, Tom R. said: All of the data entry on the lease layout is done using global fields This is probably not a good idea - see here why:http://fmforums.com/topic/47273-portal-filter-and-highlight-row/?do=findComment&comment=221213 I didn't understand the rest of your description. If - as it seems - you want to lock a record without actually editing it, you can do so by using the Open Record/Request[] script step. Edited November 7, 2015 by comment 2 Link to comment Share on other sites More sharing options...
Tom R. Posted November 7, 2015 Author Share Posted November 7, 2015 Thank you for the reply. The Open Record/Request script step does exactly what I need. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 3064 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 accountSign in
Already have an account? Sign in here.
Sign In Now