Re: database write error

2012-02-01 Thread Bernard Devlin
in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4345754.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url

Re: database write error

2012-01-31 Thread Mike Bonner
]]', \ '[[tmaternaldob]]', [[tcareprovider]]', '[[tnote]]')) into tCmd revExecuteSQL gConnectID, tCmd Thanks -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4343759.html Sent from the Revolution - User mailing list

Re: database write error

2012-01-31 Thread Len Morgan
Apostrophe is a reserved character in SQL so you'll have to escape it. If you take the part of your INSERT statement that has the field with the apostrophe in it and expand the variable (i.e., write it in with the *contents *of the variable instead (e.g., INSERT .,'[[globaldata] ]'

Re: database write error

2012-01-31 Thread Ken Corey
On 31/01/2012 12:32, Len Morgan wrote: Apostrophe is a reserved character in SQL so you'll have to escape it. If you take the part of your INSERT statement that has the field with the apostrophe in it and expand the variable (i.e., write it in with the *contents *of the variable instead (e.g.,

Re: database write error

2012-01-31 Thread Bob Sneidar
]]')) into tCmd revExecuteSQL gConnectID, tCmd Thanks -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4343759.html Sent from the Revolution - User mailing list archive at Nabble.com

Re: database write error

2012-01-31 Thread Pete
Two different topics here, I think, - escaping single (and double) quotes and sql injection. Both appear to be solved with the revExecuteSQL substitution. If you don't use revExecuteSQL solution then there's two choices for escaping. SQL accepts either single or double quotes to enclose

Re: database write error

2012-01-31 Thread Mark Smith
again for the great suggestions. -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4345697.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode

Re: database write error

2012-01-31 Thread Mark Smith
you replace the outer quotes with single quotes as well? -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4345754.html Sent from the Revolution - User mailing list archive at Nabble.com

Re: database write error

2012-01-31 Thread Pete
not know where the string beings/ends??) Or can you replace the outer quotes with single quotes as well? -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4345754.html Sent from the Revolution - User mailing list archive

Re: database write error

2012-01-31 Thread Mark Smith
. -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4346808.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode

database write error

2012-01-30 Thread Mark Smith
-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4343759.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe

Re: database write error

2012-01-30 Thread Mike Bonner
]]', '[[tmaternalphin]]', '[[tmaternalmhsc]]', \ '[[tmaternaldob]]', [[tcareprovider]]', '[[tnote]]')) into tCmd revExecuteSQL gConnectID, tCmd Thanks -- Mark -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/database-write-error-tp4343759p4343759.html