Hi,

we are having problems with 1585 update conflict errors.

The thing is that this error simply should not exist in our case.

We have table buffering (5) enabled and are adding records
to several tables. We are not doing any update. We simply
do an append blank and replace fields.

Sometimes (very seldom) we get this 1585 error (always in the add mode).
This happens in single user environments with one form open as well as in network environments.

I'm a bit worried if it makes sense to use the force option
in a table update. This would be a good choice if there were a
bug with the firing of this error. On the other hand I'm afraid to use "force"
that this error may have its good reason and I will overwrite
some data.

Thanks in advance for any suggestions.

(I canot switch to Insert SQL in the short run).

Andreas