If you do a commit() on the connection after the insert or update and don't
get any sqlErrors it should be there.

When you have multiple clients accessing mutiple tables like this you can
get all sorts of weird timing effects if two users happen to access the
records at the same time.

The probability is low unless the system does a lot of transactions, but it
is possible.

Is there any particular reason you are not using the server's ability to
shadow to do this automatically?


Rick

----- Original Message -----
> All I need is to know if an inserted records really IS inserted and
> will stay so (and gets saved to harddrive) :)
> Thank you again!
> John