K
Ken Ward
Guest
I was honestly expecting something like this as well. It turns out that I could use the CATCH exception handling to trap this error as well, but the SEEK solution is cleaner-looking.
Continue reading...
Continue reading...