Tips and Tricks for the Xojo Developer
Issue: 13.1 (January/February 2015)
Author: Markus Winter
Author Bio: Markus is a Molecular Biologist who taught himself REALbasic programming in 2003 to let the computer deal with some exceedingly tedious lab tasks. Some call it lazy, he thinks it smart. He still thinks of himself as an advanced beginner at best.
Article Description: No description available.
Article Length (in bytes): 9,233
Starting Page Number: 87
Article Number: 13111
Related Link(s): None
Excerpt of article text...
Programming is fun. Bug hunting is not. I just spent the last two weeks weeding out bugs in my app, and I've come to realize that I really don't give enough credit to the Xojo guys for fixing all those bugs that I keep moaning about. So guys, this one is for you:
thank you!And keep up the good work... ;-)
Tip 1: Break on DB Error
In Xojo you have the option to break program execution when an error occurs (it's in the project menu), usually giving you instant access to the offending code and allowing you to fix the error.
However this does not happen if you work with databases and your SQL is wrong. The database will throw up an error that is NOT caught by the debugger, so you usually check for it with something like this:
db.SQLExecute( someSQL )
...End of Excerpt. Please purchase the magazine to read the full article.