Development Team Blog

As soon as the [URL="http://support.dataaccess.com/forums/blog.php?b=74"]previous article[/URL] was published, I realized that some examples would go a long way to illustrate the point. Of course, I wrote it a week ahead, but didn't think of adding examples until the same day it was published... Oh well, we've all been there... So here are some real-world examples of what I was talking about.

[B]Start Center[/B]
A few years ago when the Start Center in the Studio ...

I very often see questions like "How can I find out if doing xyz will work?". Often that's in disguise for a more straightforward problem like "Sometimes when I do xyz I get an error, I just want to suppress the error and do something else instead."

That original problem should lead you to think: "I know, I'll check for the error and handle it". But all too often it turns into "I'll figure out if doing xyz is going to succeed first, and then I do ...

Did you know that any object can turned into an error handler object? An application can have one error object at any one time. That object is the object identified in the [I]Error_Object_Id[/I] global handle. Anytime an error occurs the [I]Error_Report[/I] event is sent to the object Id in [I]Error_Object_Id[/I]. If you change the value of [I]Error_Object_id [/I]that new value will become the error object and, upon an error, receive the [I]Error_Report[/I] event. That’s all there is to error handling. ...

You know when there's a program error, and you get that pesky error dialog that says something like [I]Error foobar Technical Details Error Number 1234 Instruction Address 5678[/I], and an OK button. So you think to yourself, great, there's an error in the program, now what? If you're lucky enough, this happens during development while you're debugging, before anyone else sees the problem. If you're not so lucky it happens at a customer site. When this happens at a customer site, you can try to ...

Attached Thumbnails