>>>I know you know a lot more about this than I, but I've been using it the way I noted for several years without a problem under Win95. Perhaps this is an NT problem?
>>
>>I take that back, I just tested on NT and it's fine, also - and I know it's fine on Win98, also. Maybe the Netware is a problem, then?
>
>Bruce, what you've effectively done is shoot VFP with a poison dart. It will in all likelyhood stagger around and fall over in some other (seemingly) totally unrelated piece of code. Up to this point, I'd say you've just been lucky! In general, I think this is probably the majority of the problems with Windows, some pointer gets corrupted, (or variable treated like a pointer) and causes problems elsewhere. Usually extremely difficult to find, unless it generates a C...5 error. A timebomb just waiting to go off later!
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.:-)
George
Ubi caritas et amor, deus ibi est