J
Jarek
I am currently developing a VB6 program which uses MS Access over DAO.
When I issue an SQL statement which contains a syntax error, my VB error
handler jumps in and I can rollback the transaction. So far, so good.
But, when there is a constraint violation, the SQL statement still fails,
but no VB error is being generated. I cannot trap this situation, I cannot
rollback the transaction. I commit, and then the database is corrupted.
What can I do?
When I issue an SQL statement which contains a syntax error, my VB error
handler jumps in and I can rollback the transaction. So far, so good.
But, when there is a constraint violation, the SQL statement still fails,
but no VB error is being generated. I cannot trap this situation, I cannot
rollback the transaction. I commit, and then the database is corrupted.
What can I do?