>>
>>See the series that Ed Rauh and I wrote for VFUG (beginning last Sept.). That first article will answer this question and others.
>
>I skimmed the first article. Thanks. Seems to me WSH is probably calling the MPR.DLL. Since our installed base is huge, and I can't guarantee that WSH is installed on all the computers, I think it might be best to go right to the source.
>
>Regards,
>
Jim,

I understand completely. The WSH is undoubtedly interfacing with MPR.DLL (and quite a few others as well depending on the object).

I deal with with a lot of Win95B boxes. My post-setup executable checks for the presence of the WSH and, if not found, does a silent install. Given the additional functionality and the reduced code to maintain, it's too good a tool not to take the extra few steps to insure that it's installed on the target machine. I think that if you read over the series (which just deals with the additional functionality it can provide VFP basically) you might come to the same conclusion.