Ok, I read the article, but I'm still missing something. It seems like his error handler either takes care of the error itself or passes it to its parent. I need it to pass the error back to the code that caused it. I don't want to close down the whole application if it hits an error, I just want to tell the user that what they tried to do didn't work. Maybe if I got more specific, that would help?

I have a class that handles fetching data. The method that gets the data calls another method to open the table. If for some reason the table can't be opened, I need the first method to know that so it doesn't try to retrieve the data. Then that method tells its caller that it couldn't get the data because it couldn't open the table.

If I have the error method in the open table method tell the user that it couldn't open the table, it messes up the whole n-tier thing. So I need to know how to get the error message from the error method back to the open table method so it can pass it back to the get data method and from there back to the UI layer.

Does that make sense?

Thanks,

Michelle


>Hi Michelle,
>
>It was nice meeting you at GLGDW. Doug Hennig has a good article on VFP error handling on his website, www.stonefield.com