In part 1, I listed six scenarios that could potentially cause ExecuteSQL code to break: …and managed to get through the first five before running out of steam. This time, we’re going to look at #6 on the list, as well as some other observations, and I invite you to download and follow along in [...]

Source