Error Handling & Logging

[FileMaker Magazine]

No Access? Watch the preview video here. ErrorHandling2013_Pre.mp4

Attachment	Size
ErrorHandlingLogging.zip	84.77 KB

By Matt Petrowsky

If your FileMaker solution doesn't currently have any type of error handling built in, there may come a day when you need to know what's going on. Especially when things don't work as expected. You see, here's the crux of the situation. While you can certainly control the behavior of your solution and how things work on the inside, you can't control the external operating system and other aspects beyond the guts of your own solution.

What this means is your Export Field or your Import Records script step may break on one given client for some reason or another. You've also built logic into your solution in which inevitable dependencies exist. If script A must run successfully, in order for the follow-on script B to run as well, you need to trap for any possible errors which may happen within script A. This is when you need your own error handling for your solution - beyond FileMaker's error handling for it's own environment.

Since error handling is one of the more boring aspects of programming, it's beneficial to have an easy-to-use and quick-to-implement system which can be added to any FileMaker solution. This technique file and video provides just such a solution!

Tags: 

• Error handling
• Logging

View the full article