Hi Dan,

SET EXACT has no effect on SQL commands that TABLEUPDATE uses behind the scene. Try

SET ANSI ON

>i am having an issue that i was wondering if anyone had encountered or had a possible workaround/solution. i have a buffered view with a memo field that will only generate a conflict error on the memo field when a second user has modified the contents completely. if the second user modified the contents by appending text, tableupdate will not see the difference and the changes will be overwritten. the view has comparememo set to .T. and update is set to update key and modified. SET EXACT does not seem to have an effect. REFRESH() causes CURVAL to return the new text, but it doesnt have an effect on the TABLEUPDATE command. i have checked to make sure that the buffered memo field is marked at modified before TABLEUPDATE is called. it is also correctly marked as updatable in the view. all other fields correctly trigger a conflict error. any ideas would be much appreciated.
>
>thx.