Sorry - I was hoping for something like a variable (i.e. "vbNoData" or some representation) for the error - just in case Microsoft decides to change the value from 2501 to 2502 or 2503 or some other value in the future. I just do not like having "magic numbers" in my code. I've currently set up my own variable but just thought Microsoft has already defined the error codes somewhere.
Thanks,
Karla...
Leave a comment: