Bill,

Glad to be a part of exchange. *s*

>Doug,
>
>>I can see why you work for a logistics company. *g*
>
>< bg > Actually, the company name is in reference to the owner coming from the transportation industry, before getting into the computer biz. I, on the other hand was afflicted with too many syllogisms and whatnot in those college Logic courses, and it jumps in from time to time when I am not looking :)
>

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*


>>You're absolutely correct. Exception programming is the answer IMO here.
>
>I think this is the best part of participating in these online discussions, getting hold of the correct terminology. Exception programming is a much better way of saying what could be done here, and now I can go read up on Exception programming techniques. Am I correct in assuming this would include things like the C++ try/catch/throw constructs? I always thought that kind of stuff was really cool! :)
>

Don't really know much from that angle (I'm not a C programmer - my life is too short *g*) but you got me thinking about the problem from another angle and that was good. It's more of a management problem than a VFP printing problem.

For me, exception programming is also pretty much the same as defensive programming. Or, how to create the most stable application that can take constant abuse from people who just want to get their job done. I think Jim Booth and Whil Hentzen have discussed this under the topic, "User Hostile Interfaces". *bg*


>>Good call.
>Thanks for the vote of confidence.
>
>>Best,
>And to you as well,
>Bill

Best,

DD