:thumbsup: Generally it's a very good idea. But the thing is this. I have a production app(scanners and all that) and normally a interface for setting up the lines,projects... I did not allow them to delete a PN. Now they want that feature. But in order to not delete any production data I need to check if any production data exists for that PN and if not, then and only then delete all stuff related to that PN. Else refuse it. Yeah I know SQL would return an error complaining about FK and stuff but I don't want the user to see that. So first check and if not exists then delete. Else show a message to the user that production datas exists for that PN and delete has been aborted. :)
All the best, Dan
modified on Thursday, June 9, 2011 5:05 AM