Bob Sneidar bobs at
Tue Aug 10 16:17:32 EDT 2010

Agreed. In fact, I put all database operations inside a try/catch structure so as not to assault the end user with error dialogs that they don't know what to do with. If you are making a TON of calls in your app, you may want to consider writing a special database error function which knows how to handle all the errors you want in a way that the end user (and your app) can work with. 

For instance, a "Database temporarily unavailable. Try again?" dialog that gives the user a chance to call IT and have them get the DB back online without dumping your app mid transaction. 


On Aug 10, 2010, at 1:13 PM, Mark Schonewille wrote:

> Peter,
> The last db operation. If no error occurred, it is empty. Actually, I thought this function was obsolete, but I might be wrong about that. In any case, I'd always check the result after using a database command or function besides any dedicated error reporting functions.
> --
> Best regards,
> Mark Schonewille
> Economy-x-Talk Consulting and Software Engineering
> Homepage:
> Twitter:
> KvK: 50277553
> From 15th August, we'll have time for new projects! Be the first in line and contact me now!
> Download the Installer Maker plugin for Runtime Revolution at
> On 10 aug 2010, at 21:57, Peter Haworth wrote:
>> Does this function return the result of the last db operation or the last db operation that failed?  The dictionary entry seems to suggest the latter...
>> Pete Haworth
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list