>Does anybody know if there is a bug/limitation with the Visual FoxPro ODBC
>Driver version 5.00.00.00412 with regards to the data size in memo fields
>when using the Update SQL command?
>Using MsQuery32 I execute the following command - UPDATE html SET sectname
>= 'Default', section = '
...', filename = '' WHERE (html.page_id = 1)
>
>I reduced the data in section field of the update command for this message
>however the field section is a memo field which contains more than 255
>characters.
>
>After issuing the statement I get the error "[Microsoft][ODBC Visual FoxPro
>Driver]Command contains unrecognized phrase/keyword."
>If I reduce the section field data so it only contains 255 or less
>characters the Update statement executes successfully.
>
>Any suggestions?
Foxpro (in any of its incarnations) had some limitations on strings. You
can't have a literal string within any command line exceeding 254 or 255
bytes. You can easily split it by inserting a " + " (quote, plus, quote)
somewhere in between, or by building your string in several parts, like
cString=[UPDATE html SET sectname]
cstring=cstring+[ = 'Default', section = '
...', filename = '' ]
cstring=cstring+[ WHERE (html.page_id = 1)]
This helps just for the fox side of the problem; if there's another
similar limitation in the ODBC side of the process... keep this thread
open.