![]() Try/ catch blocks should actually be relatively rare, because there are relatively few errors you can really recover from. Where I don't even do anything with it, as I don't feel a need to.Ĭontinuing after errors as if nothing's happened is a terrible way of programming.Ĭan't work out the new balance of the account? That's okay, let's just store it as 0. I'm thinking something like this: Dim zRange As Range Is there a Try-Catch which I can use for a line like this? I've also found (and known for a while) that On Error or GoTo lines are considered poor coding. Set zRange = commentsColumnRange.SpecialCells(xlCellTypeVisible) I ask because I'm using the line in my program, but I don't want it to Resume Next all the runtime errors which occur, just the obvious one on the next line.Ĭall FilterTableFor(fieldNameColumn, Array("baseunitprice", "burden", "MTLBURRATE", "PurPoint", "Vendornum")) ![]() On the Microsoft site, I found this sentence: "An On Error Resume Next statement becomes inactive when another procedure is called." What exactly does this mean? What is considered to be a procedure? I'm reading up on how to use On Error Resume Next and I'm trying to figure out how long that line will apply to the program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |