Yes, in VFP you cannot create OCX (I think I mentioned that in an earlier post). And, I agree with you that this invalid procedure name business is really unfortunate -- after all, it's not like you will ever be referring to the code as "Close()" -- but rather "Winsock1_Close()". In other words, the only keyword violation is at compile-time!
You think there's some way to hack around in the resulting file? I just don't know...
The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts. - Bertrand Russell
