Thanks. Nice meeting you, too. GLGDW was quite an experience. I got to see how things are done outside the world of SBT code. :) Now that I'm getting to use some of it, I'm finding there's a whole lot about OOP code that I don't know. I'm trying to balance learning how things are done with actually getting things done. It's been interesting.
Anyway, I'll take a look at that article. 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>
>>I'm finally getting to do some real OOP programming and am trying to learn how to do things the "right" way. One of the things that has got me confused is error handling. I just found out that if you put an Error method in an object that it acts like ON ERROR, which is cool. :) But I'm not sure where to go from there.
>>
>>Once the error method has control, how do I let the code that caused the error know there was a problem? I want the original method to stop processing and return the error to what called it, so somehow it has to know.
>>
>>I can think of various ways to do it, but they all seem rather kludgy. So I thought I'd ask what the usual way to do it is.
>>
>>Thanks,
>>
>>Michelle