I understood that. My point was that creating an error table was more overhead than simply adding another method to handle the error in the first place. :)

It seems strange that this function doesn't already exist. Maybe I should add it to the wish list...

Thanks,

Michelle


>If you use my code to create your error table, then you could write our function to SEEK the error number and return the message.