Jump to content

Search the Community

Showing results for tags 'record locking'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type

Community Forums

  • The New FileMaker Platform
  • Community Resources
    • Community Articles, Tips, & Techniques
    • FileMaker Marketplace Discussions
  • FileMaker Platform
    • FileMaker Interface Features
    • FileMaker Schema & Logical Functions
    • FileMaker Go for iPad and iPhone
    • FileMaker and the Internet
    • FileMaker Pro Advanced 18
    • FileMaker Pro Advanced 17
    • Legacy FileMaker Platform Discussions
  • FileMaker Server Administration
    • FileMaker Server 18
    • Zabbix Server Monitoring
    • FileMaker Server 17
    • FileMaker Cloud
    • FileMaker Custom SSL Certificates
    • oAuth and External Server Authentication
  • Brain Food
    • Security Concepts
    • The Left Brain
    • Upgrading & Migration
    • Data Analysis
    • Development Standards
    • The Separation Model
    • Relational Database Theory
    • Damaged / Corrupt File Problems
    • Bar Codes (Printer, Scanners, Software)
    • Hardware & Networking
    • OS Level Database Automation
    • Product Ideas
  • JavaScript Integration
  • FMForums Affiliates & Sponsors
  • FileMaker Classifieds
  • FM Forums Operations
  • FileMaker Friday Night Chat's Topics


There are no results to display.

There are no results to display.


  • White Papers
  • Infographics
  • Samples
  • Solutions
  • FMGo
  • Plug-Ins
  • Tutorials

Product Groups

  • Workplace Innovation Platform
  • Site Advertising
  • Development & Hosting

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start







Website URL




OS Version

Found 5 results

  1. In this article the term "self-aware window" refers to a FileMaker window that can know in real-time whether or not it is the currently selected window, and act accordingly. We introduce a technique for allowing individual windows to calculate this, and some examples of what windows could do with that knowledge. Read the Full Article Here…
  2. How does Mirrorsync deal with potential record locking (due to record being in use by another user) during sync? Also, how are any interruptions handled during sync, say a network disconnect? Thanks, Andreas
  3. Hi all With the amount of scripts and users I now have it's time to look seriously at record locking implications. Any pointers greatly appreciated! I have a Labour, Items and Invoices table (Labour and Items are actually in the same table but are generally treated as though they were in separate tables). A Labour record has multiple Item records assigned to it. Items can only be added via a portal within the Labour record layout. Labour and Item records are assigned to an Invoice record via the Invoice_IDF field. The assignment process is done by a script that is run once a month, this script is run when everyone (apart from the user running the script) is out of the database, so record locking is not an issue in this case. Where I need advice is when labour/items are being manually added/removed to/from newly created invoices. There are two ways that this works: 1. Within the Invoice record: There is a portal displaying both uninvoiced items and labour (as they are actually in the same table) A button within the portal row is clicked, and all the relevant records are assigned with the Invoice ID of the currently open Invoice Record. e.g. if an Item is selected, then it is given the Invoice ID - this Invoice ID is also assigned to the Labour record that that Item it is attached to, and any other Item records that are in that same Labour record. 2. Within the Labour record: There is an 'Invoice Assignment' button. When this is clicked a dialog pops up with the invoice_ID field. The user then populates/blanks the field and the labour and item records' Invoice_IDF is populated accordingly. How can I safely run these assignment scripts so that they don't do half the job - for example assigning the labour record but not the items record because someone is editing it. If it is advisable/simpler for the second method to be done away with (and add the option to 'unassign' labour/items via the invoice record in the 1st method) then that can be done. TIA
  4. I have a multi user db and I'm finding that people are locking records b/c they are leaving the cursor in a field after doing a specific task. Is there a way to script all fields to have NO focus after a task is complete? I have tried to change focus to other objects on the screen, like a button, that do not use a cursor but the file remains locked. Any thoughts? Jason
  5. Hi all I've just had this request come through. I'm quite sure this is something that is beyond the call of duty, but thought I'd check to see if anyone has any suggestions: Often users modify a field but remain in that field, they do not commit the record by clicking the blank space on the layout. Obviously this means that that record is locked so no one else can modify it. The suggestion has been to have an automated timer commit script. Off the top of my head this would probably not solve the problem if the record cannot be validated because of other fields that need to be populated (which would happen around half the time I'd say). My instinctual position is that if there's one thing we're allowed to request from the end user it's that they don't loiter around in fields! Any thoughts welcome. Thanks
  • Create New...

Important Information

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