Why would you not want to check for the instance of the key before
removing.....thus no error would happen? Code to avoid errors (defensive
coding) can prove to be more efficient too.

On Error GoTo ERR_HANDLER
If Not myCollection("key1") Is Nothing
myCollection.Remove
EndIf


"BW" wrote:

Hello,

For some reason when i try to remove a key from a Collection where that key
hasn't been added yet, i cannot trap the error when it occurs within an error
handler. All i get is a error dialog box that pops up that says "Invalid
procedure call or argument"

the code snippet is as follows:

On Error GoTo ERR_HANDLER
myCollection.Remove ("key1")
.
.
.
ERR_HANDLER:
.code here does not get executed when "key1" does not exist in myCollection.

How i can trap this error and continue processing?