CommandTimeOut ignored by oracle's OLEDB provider

I am using ADO 2.6 with oracle's OLEDB provider for oracle (not the microsoft one).
Whatever value I set for the CommandTimeout property of the connection, or of a command object, no timeout occurs.

It seems that the OLEDB provider did not implement the CommandTimeout property.

When an update statement is executed, and runs against a lock, the statement waits untill the lock is resolved.

I want to inform the user that the data is locked, and that he should try it at a later moment, but when the Execute method doesn't timeout, I can't do that.

Does anybody know how to cancel the update statement when it times out waiting for a recordlock?