Change

WITH loPing.oleSock
* To
WITH loPing.oleSock.Object

>>I believe that mskb #Q192693 applies to the winsock problem. Subclassing
>winsoch should resolve it.
>>Do you create second class (mscomdlg ) at design time or runtime?
>
>Hm. Well; no I just create teh object, like I create an object for word.
>
>createobject("mswinsock.winsock")
>
>I'm not using the vfp "setup wizard" for distribution.
>
>Ok; that said; I did try "subclassing" it and got the poor results.. I'm frazzled, so forgive me if this wasn't right.
>
>http://www.jassing.com/temp/ping.zip contains both original PINGX and subclassed PINGY versions.
>
>on my dev box: pingx works quickly.
>on my dev box: pingy hangs.
>On my test boxes, pingy gives the same results as pingx
>
>I tested with
>?pingX( "levelextreme.com",80)
>?pingY( "levelextreme.com",80)
>
>Thanks for looking at it.