05-14-2023, 04:46 PM
b ..That's a great routine to id the error and line. I have used it in the past, and to it, wouldn't it be nice if the "Possible Causes" came with it? For me it's actually getting to the offending line. At the bottom of the IDE, often I just need to click on the STATUS description and it takes me right where I need to go and when your code is multi lines it's very helpful. There is an option under Search to go to a line, which is what I use, so I'm pretty well spoiled with the IDE the way it is and I put up this post in frustration from this mornings coding session as I changed the wrong For Next code, and if that wasn't bad enough, to fix the out of range script I had to find the actual line that was trigging the damn array being out of range in the first place. Lots of time waisted. There is a disconnect between the speed of my brain and the speed at which my fingers can type errors that my brain can't catch.