>>>Has anybody else hit this?
>>>
>>>We have upsized an app from VFP DBC to SQL. The SQL tables have memo fields and all is fine. We now use a DBC with remote views instead.
>>>
>>>However... if there is a bracket ([ or ]) in the memo field of a SQL table, we can no longer save (TABLEUPDATE(.T.) returns a .F.)! And once the data is in the SQL table, we can SELECT it, but then even if we edit the memo to remove the bracket(s), it's no good because the SQL tables just won't accept the save.
>>>
>>>This seems to be the ONLY characters this happens with! Has anyone else seen this behavior?
>>
>>This may help:
>>
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/acdata/ac_8_con_03_9rar.asp
>
>I find it interesting that no other characters I put into these fields (text fields -- memo to use VFPers) had ANY effect other than the brackets. But brackets in those text field cause subsequent TABLEUPDATE(.T.)s to fail.
>
>Can someone else try this on another install and tell me if it is just me?

I see the same problem. Updates work fine until there is [ or ] in the SQL table; after that TABLEUPDATE() returns .F.. VFP7 SP1 working against MSDE2000 on W2K SP3.

I updated my previous post to point you towards Identifiers...Delimited Identifiers in the BOL which might be part of the problem but it looks like the update didn't work. Sorry about that.