Hi Skip.
I usually step through my code the first time I make a call to a database, and
just before executing the SQL, I copy it and paste it into an SQL utility, most
of which have a syntax checker built in.
Bob
On Jul 8, 2012, at 7:16 PM, Magicgate Software - Skip Kimpel wrote:
> Thank y
Another technique is to wrap your call in a try catch statement like so:
try
revExecuteSQL tDBID,tSQL
catch theError
answer "There was an error accessing the database" & cr & theError with
"Cancel" or "Continue"
if the result is "Cancel" then exit to top
end try
Bob
On Jul 7, 2012, at
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
> 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 s
Hi Skip (and welcome to liveCode from me too...)
If you want to check if there was an error in the SQL statement you tried to
execute, you will want to check "the result"
revExecuteSQL tDBID,tSQL
if the result is not a number then
-- an error occurred
answer the result & cr & tSQL
end if
Th
How would I call for an error, for instance on a revExecuteSQL database call?
For some reason it is not writing to the database and I am trying to
figure out what is causing it to fail.
SKIP
___
use-livecode mailing list
use-livecode@lists.runrev.com
P
