Hi,
I am new to using oracle with VB. I started going the route where I use VB and only use oracle to populate record sets (no parameter queries or stored procedures of triggers). I found that the errors returned to VB were terse and didn't specify which table field was affect. For instance, if I had more than on NOT NULL field, all I would get was an error saying that "some field" had violated the not null constraint.
So I turned to using stored procedures for DML. I chose triggers since I could return the name of the field affected, but testing exceptions (such as violations of uniqueness constraints) seems impossible. I am confused as to how to get decent error messages back to vb with the names of the fields affected. Any suggestions?
Thanks,
Neil
I am new to using oracle with VB. I started going the route where I use VB and only use oracle to populate record sets (no parameter queries or stored procedures of triggers). I found that the errors returned to VB were terse and didn't specify which table field was affect. For instance, if I had more than on NOT NULL field, all I would get was an error saying that "some field" had violated the not null constraint.
So I turned to using stored procedures for DML. I chose triggers since I could return the name of the field affected, but testing exceptions (such as violations of uniqueness constraints) seems impossible. I am confused as to how to get decent error messages back to vb with the names of the fields affected. Any suggestions?
Thanks,
Neil
