>>>>Hi Fred,
>>>>
>>>>I'm absolutely astounded that VFP isn't blowing up, but I agree with you on this. In fact, I'd rather it did blow up than work. It'd tell me right away that I was doing something wrong with the call. If you're scenario came to pass, I'd probably be cursing some innocent device driver or something.:-)
>>>
>>>I speak from the voice of experience on this. Way back I had used some API stuff and THOUGHT it was working OK. Then, it just started crashing somewhere else in the code. The only change had been that the contents of a variable had been changed (it was used in the API call). Experimenting with that information, I was able to make all sorts of strange behavior occur by moving the line that the variable definition occured on, etc. Finally pinned it down to a length problem, but it was wrong initially, it just *seemed* to work OK. And no better truth has ever been spoken, I'd much rather see it fail then work for the wrong reasons! Not that Device Drivers are innocent, or anything like that, though! ;)
>>
>>I do have this tendency to blame myself first when a program GPFs. 99 times out of 100, it's the stupid programmer's fault (meaning yours truly). But you're right, many device drivers (especially HP's) are anything but innocent.:-)
>
>Tendency!?! For me, I usually can guarantee that a fatal wound is self-inflicted! :) (HP drivers excepted)

ROFL. Same here!