Doug,

>Well, formal logic kind of puts me to sleep but what we do in our profession >
>is more of a kind of practical logic - IOW, what works? *g*

I agree completely. All computer work is based in logic, and we are definitely not dealing with academic issues (most of the time). Logic drove me crazy at first, but eventually those classes turned out to be my most useful.

I am not a C programmer either, I kinda use it like Latin- I don't write it, but I find it helpful to be able to read it from time to time (not that I can read Latin, but you get the idea *s*). Its useful for studying things like design patterns and a lot of other theory-oriented material that I come across. The try/throw/catch construct is just a way to wrap a piece of iffy code and define a handler to take care of problems, kinda like a transaction, which is maybe why there isn't really a need for it in VFP.

>For me, exception programming is also pretty much the same as defensive programming

I see what you mean. Its almost like they're the same except for a difference in scope. You could say defensive programming is a low level technique to make your code as responsive as possible to unexpected bugs, wheras exception programming makes its as responsive as possible to unexpected, or unreliable user actions. < bg >

Thanks for the heads up on the Jim Booth book. I have been looking for an excuse to get it, but I keep backing it up for other stuff. This looks like a good excuse. My wife will thank you for suggesting it. :)

Anyway, I am digressing, none of this is helping Andrus, so I will quit rambling now *s*

Best,
Bill