What would be the most elegant and/or appropriate method to enforce/implement Primary key constraints in Visual Basic for an Oracle Database both composite and single ?
I'd like to gracefully alert the user that their set of data(which constitute the primary keys) is already present in the database - Should I query the table(s) before saving the record ? or else how ? Thank you,
RR.
__________________________________
The best is yet to come.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.