My customers are running into an intermittent problem.

They will search for a record by the table's primary key (it uses a
TIBOQuery). The search comes up as zero records found. So, then, they try
to add the record (calling Insert on a TIBOTable connected to the same
table, filling in the data aware controls, then calling Post()). This
produces a Key Violation error. They try the search again, and it still
says it isn't there, but every time they try to add a record with the same
key, they keep getting the Key Violation.

If they exit my app, start it again, and try the serarch again, it finds
it. So, it looks like it was there all along, but for some reason, the
search wasn't finding it. I'm not sure why restarting my app makes it
start working.

This problem doesn't always happen. The customers are doing this process
(search; if it's not there, add it) all day long, and it's happening maybe
5-6 times per day. Sounds like some sort of glitch. Both the TIBOQuery
and the TIBOTable are using the default transaction, so I don't think
that's the problem.

Oh, also, sometimes, instead of the search coming back with no records
found, it will say that it found it, but when it displays it, the record is
completely blank, including the primary key field (also blank).

Does anyone have any idea what's causing this, or how to fix it?

Thanks,
Joe