I can catch the exception with a Try but how to cancel the move to a new row and to force user to correct the edited row?
What i would obtain is a "SQL Server Management Studio-style". When you edit a row and move to another, if an exception is detected (duplicate key for example), a message is shown, the edit glyph is mantained in the edited row and cursor remain on the edited row.
Does anybody know if there is a performance difference between these two example queries:
SELECT * FROM tblFox WHEREstringFieldValue IN ('Ring-ding-ding-ding-dingeringeding!', 'Wa-pa-pa-pa-pa-pa-pow!')
SELECT * FROM tblFox WHEREstringFieldValue='Ring-ding-ding-ding-dingeringeding!'OR stringFieldValue= 'Wa-pa-pa-pa-pa-pa-pow!'
I would Google it if I knew what to enter to get a relevant answer...
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
I did not know exactly that there is performance difference. But query using IN will reduce your typing and looks good. If there are few more data to search in OR condition, You type field name again and again??
If you are using SQL Server, you could use "Show Execution Plan" and see if there is a difference.
If you are using Oracle, I believe there is a 1000 element limit to the "IN" clause. At a previous company I worked for we got bit by this. (This was a while ago, maybe Oracle 9, it may not be an issue now)
Last Visit: 31-Dec-99 18:00 Last Update: 19-Dec-13 19:04