>>Thanks Ed that worked perfectly. One more question. How do you figure out where these properties are when all
>>you get is that kind of message. I don't mean specifically but more what proceedure do you follow?
>>
>
>In this case it was instinct - I know where MAINHWND, _WHTOHWND and _WONTOP live...one advantage to using the FFC is you've got the full source; open it with the class browser, look at the code, and look at the code for the class (in this case , videoplayer - you'd have found this code fragment in the openvideo method:
*!* Need to use window handle functions in FoxTools
>SET LIBRARY TO HOME() + ".\FOXTOOLS.FLL"
>EXTERNAL PROCEDURE MainHWND
>EXTERNAL PROCEDURE _WhToHwnd
>EXTERNAL PROCEDURE _WOnTop
>
>
>>Terry
>>
>>
>>>>I dropped the Soundplayer component on one of my forms and when I rebuilt the project I got the following:
>>>>
>>>>Visual Class Library c:\program files\microsoft visual studio\vfp98\ffc\_multimedia.vcx has the following errors:
>>>> Proc./Func. MAINHWND - Undefined
>>>> Proc./Func. _WHTOHWND - Undefined
>>>> Proc./Func. _WONTOP - Undefined
>>>>
>>>>What's missing?
>>>>
>>>
>>>FOXTOOLS
Thanks, seems fairly obvious when you spell it out.
Terry
It is impossible to make programs idiot proof. Idiots are too cleaver.
MCP( Tcp/Ip )