>I will take a look at the netresources download. The scripting host is not the friend of the average banker. We have to work under the assumption that it is not installed on any of the pc's. Since we need to install parts of IE for the app to run, we will try to sneak the scripting host in. I'm glad to hear that disabling it, won't stop us from using it.
>
>Thanx.

Anytime, Fred. Actually, the WSH is basically batch files for Windows. Of course, they're on steriods.< bg > Folks have to realize this, and that even in the old DOS batch file, you could force a hard drive to be re-formatted. There, you didn't have the luxury of removing the cause, command.com. I personally believe that a little education and a little responsibility on the part of the end user would be a much better solution than trying to circumvent the WSH.

In prior to Win2K, it was either an optional component or part of an NT SP. In Win2K, it's a normal part of the environment. Given that, folks are either going to have to learn to live with it, or obsolete and eventually unsupported software.

>>>Is there a way to pull the UNC path for a shared network printer that is not setup on the current PC? We need to pull the UNC path in the app running on WIN 9x and NT clients.
>>>
>>>BTW, Scripting host is disabled for security reasons.
>>>
>>>Ideas?
>>
>>Ed Rauh's NETRESOURCE programming might be able to do this Fred. It's in the download section here at the UT.
>>
>>BTW, I'm not sure if you're aware of this or not, but simply removing the wscript.exe and cscript.exe programs does not disable the WSH from within VFP, but only prevents the running of vbs, vbe, js, and jse files.