Even Easier Error Logging
About 10 months ago, I released a video and file about Error trapping and logging. Since that time, I've improved my system and made it even easier to log the errors. As I mentioned in the previous article, it's really nice to see where errors are happening. You get a much clearer picture of any issues when they happen. When it comes to users, knowing as many details about the error the better - it sure does beat the conveniently vague "It doesn't work".
So you start using Set Error Capture [on] and you think you're good to go with Get ( LastError ). This is, of course, until you start performing multiple steps within one script which could cause errors and you want to log those errors to a log in order to review them.
Being notified about when an error happens and what type is also nice. Wait, "type of error"? Isn't FileMaker the only potential for an error? Nope, not quite.
You can experience any number of errors in your FileMaker solution. FileMaker errors, plug-in errors, custom function generated errors and your own application errors.
This means you need a robust system for handling and managing these errors. Fortunately, I've given you a great head start with this video and technique file!
Comments
Good Stuff
Wow, I had just shown something very similar to this last night at our user group. I like how you're getting the data into the error fields and how easy it is to add new fields to the log. I'll have to make some small changes to my logging routine. :)
Thanks!