> Another strange occurance is that the first record
> always posts. But any other posts or deletes
> subsequent to the first creates the error. Could
> it be transaction related? I am using default
> tranaction with isolation=tiCommitted. If you
> need more info, email me the request, and I'll
> send it as soon as possible.

When you say that you are using a "default transaction" - do you mean
that you do not have a separate transaction component, that you are
letting each query create its own internal/default transaction?

Such an arrangement is very likely to give trouble with master/detail.
The exact nature of the trouble probably depends on IBO internal
timings, which could explain why the problem shows on network and not
local connections. It is a strange error to get for this situation,
it would be interesting to see a demo app showing the problem - just
to see what is happening.

Anyway, the point is... Make sure that every query in the
master/detail setup uses the same transaction. That is; drop a
separate transaction component onto the form (change its isolation to
tiCommitted) and attach each query to that transaction. Does this
solve the problem?

If not solved, will definitely need a demo app showing the problem.
(As I said above, it would be interesting to see one anyway.) Also,
are you using TIB_Query or TIBOQuery or what?

HTH

Geoff Worboys
Telesis Computing