Calling for database error

[Magicgate Software - Skip Kimpel]

Thank you Malte and Mark... that is exactly what I was looking for and
it worked like a charm.   I was trying to build some SQL statements
and was missing a few "," instances which was causing it not write the
record but was not giving me any notification that something had gone
wrong.

NOW I know how to call for that!

Thanks!

SKIP

On Sat, Jul 7, 2012 at 12:35 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:
>> The result is quite often your friend. The other friend you will
>> stumble upon sooner or later is the variable "it". Makes sense to
>> check those two.
>
> Another hint (and you may be doing this already) is to make sure the
> database id from the open command is a number. If it's not, it's an
> error string telling you what went wrong.
>
> --
> -Mark Wieder
>  mwieder at ahsoftware.net
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode