In FileMaker you can load content in web viewer boxes. While useful, they load at a different pace than the rest of the record they are in. For detecting the load of an image in a web viewer I use the following code.
When creating loops that traverse through all the records of a found set, most all of us use the useful “Go to Record/Request/Page [Next; Exit after last]” function. It’s quite nice, since it prevents a loop from continuing into infinity when you reach the last record of a found set. However, you will always get an Error 101 from this.
Error 101 is telling us that the record we want is not found. For this case, the record we want is the next record, which doesn’t exist because we’re already at the end. You would think the built in function would suppress this error when you select to option to exit after the last record, but the error still gets logged, and will pop-up if we use the debugger window or if we are running a server script. Continue reading FIleMaker: Fixing The Annoying Error 101
When editing a live FileMaker database, we’ll sometimes need to force clients to commit their records before the update can happen. If our users are on remote machines, this can be a real problem. The general fallback approach is to send a disconnect request from the FileMaker Server. This will close the database the client is using, so it isn’t the most friendly method.
Filemaker’s date field is not very kind to users…
…especially ones that like to type instead of using their mouse to select a date. However, we can fix this to make a more pleasing user experience. Continue reading FileMaker: More Useful Date Fields