Peter Haworth-2 wrote
>
> If you use single quotes, double quotes don't need to be escaped in the
> literal, and vice versa. So, if you're sure that your data won't contain
> double quotes, then you can use double quotes to enclose the literals and
> single quotes won't cause a problem.
>
> Pete
>
Thanks for the suggestion Pete. I was going to try that but the relevant
code section reads as follows
merge("VALUES ('[[globaldate]]', '[[tmaternalname]]', '[[tmaternalphin]]',
'[[tmaternalmhsc]]', '[[tmaternaldob]]', '[[tmaternalage]]',
'[[tmaternalpc]]', '[[tmaternaled]]'," & \
"'[[tmaternalocc]]', '[[tmaternalage]]', '[[tsite]]',
'[[tmaternalchart]]', '[[tcareprovider1]]', '[[tcareprovider2]]',
'[[tcareprovider3]]', '[[tnote]]')") into tCmd
Wouldn't replacing the single quotes with double quotes mess up the merge
command (ie. it would 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 at Nabble.com.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
