Search the Community
Showing results for tags 'commit'.
I'm having an issue with and offline sync setup that I created. I used the basic outline as described in the FM white paper for offline syncing. I'm using a transactional model for the whole sync process, so there is a final commit at the end if things don't throw an error. It is this final commit that is currently giving me problems. When this commit fires, all of the records that were created during the sync process are once again tagged as being 'modified', and so the modification timestamps are updating again. Here's an example: say I sync 3 records at 22:43. During the sync process
Hi friends - Back here again after many years to ask some of your first-class advice please.... I have a very old solution which I recently converted from fp7 (can't even remember which version I originally created it on) to FM12 and am checking performance. Windows Vista on a trusty old Dell laptop. There is a script triggered by a button, which pauses indefinitely for user input. Many moons ago, the script would resume when the user pressed Enter on the keyboard. Now, it will only resume if the user either 1) clicks on 'continue' in the status toolbar, or 2) presses Ctrl + E
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…