>Hi George,
>
>Thanks for the response. I don't have a problem returning the error message from the .dll. My problem is that it is a fatal error (Zip Code Not Found) or similar. This may be an error I inserted delibrately to test if the .dll would catch it and what message will be displayed. Problem is that I test several 'fatal' errors and I don't want the (I send 15 addresses some with delibrate errors) test program to continue to/thru the last test address.
>
>But the .dll considers this a fatal error and crashes. Suggestions?
>
>Regards,
>
Hi Paige,

The key question is, "Who created the DLL?" If it's from a third party (a vendor), I'd complain long and loud about this behavior, provided that it didn't also provide a method of validating the incoming data by other functions. Any well designed DLL, VFP function, application, etc. should provide a method to not only report errors, but recover from them gracefully as well. Even, in some cases, however, the Windows API functions don't do this as well as they perhaps might.

If, however, this is a VFP DLL, it's not a big deal to modify it so that this isn't a problem.