>Hi George,
>
>Your absolutely correct. The .dll in question gives property values based on house number, street addresses and zipcodes. It returns various errors regarding bad zip or bad zip+4 or no such address. Problem is that they are fatal errors. The .dll and or the address database that it uses is updated regularly and I want to run a standard test against any update/mods and test that errors are caught, msgs don't change, etc. I'm in touch with the developer regularly. The .dll is written in VB so that adds another layer of complexity. I will reach out to him. Thanks for you help.
>

You are aware the VB .DLLs are COM objects, and that you need to capture errors using the COM error handling mechanisms?