> If we look at the code of ApplyUpdates of the db it seems to
> do it all in a very controlled manner regardless if it is in
> chached updates or not.

> Please correct me if I am wrong here.

> I NEED to add that we have only moved over to not using
> chached updates it WAS previously on chached updates
> and created the SAME error.

> Thanks for the reply and help

I have no experience with cached updates, never used them.

But it seemed likely that mixing cached update methods
with non-cached updates was likely to cause unpredictable
problems. In particular there are lots of places where
the cached update methods only do anything if cached updates
is turned on.

Also, use the SQL Monitor to see what is actually going to
the server. That may help find out what is happening.

--
Geoff Worboys
Telesis Computing