We are using VFP3.0b, Win95, WIN NT server, Sybase backend.

Could someone please explain the following to me. Say I have a remote view, based on a table with a couple of fields, including an unlimited text field. When creating the view, it marks the unlimited text field
in the view as a MEMO field, which only makes sense.

Adding new records to the back-end table, via appending blanks to the view, and issuing a TABLEUPDATE() command works great, no problem. However, when an existing record is being modified, and the contents of the memo field in the view are changed, something weird happens. When the TABLEUPDATE() is issued, all appears fine, however when I try to close the view, move to a different record, etc.....anything, I get an error from the server stating something like:

"TEXT and IMAGE datatypes cannot be used in an SQL WHERE clause without the LIKE keyword..."

Now, issuing the TABLEUPDATE() with the lForce parameter as .T. solves the problem, however as the application is multiuser, I don't want to just blindly overwrite another users potential changes.

I have tried changing the UPDATES selection on the 'Update Criteria' tab of the view designer from send SQL UPDATES to SQL DELETE THEN INSERT, but this made no difference. We are using VFP30B, with Sybase System 11
as the server, with SYSYB95.DLL as the ODBC driver.

I'm not only looking for a solution, but also why an update to an existing record is so very different then adding a new record. Is the SQL Update statement the view automatically generates different in each case? Why does the server not bark at the MEMO field when adding a new record?

Thanks to anyone who can shed some light...

Mario