>What happens if the DLUD field in the second (not updateable) table is removed from the view? Does the update still have problems? Also, have you checked in the View Designer to be sure that the correct DLUD field is checked for updating?

Up to now I have discovered this :
- the problem hasn't anything to do with duplicate names (I've changed one and the problem remains)
- I'm sure I'm using correct field names and update parameters
- when I try to change other updatable fields it works !



>>I have a problem I'm fighting with since a while which I think is a bug (in VFP5.0) :
>>
>>I have a view which contains a table with several
>>updatable fields and is joined to another table (without updatable fields). Both tables have a field called DLUD (which is a timestamp), but only the one of the first table is in the view (and updatable). When I try to update the field with the common name (DLUD) I get an update conflict. Updating the other fields in the view works as expected. I'm sure I'm picking the right field. I'm sure noone else is working on the tables so there can be no update conflict !!!
>>When I force the update with tableupdate(2,.t.) then it works, as well when I use as WHERE clause only the key field.
>>
>>Anyone any idea ?