This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C8821A.E4E36ED0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have used the file scripting object in my application.

What do I need to include in my installation routine to make sure that =
all files required are installed for the user?

Sincerely

Stephen

------=_NextPart_000_0006_01C8821A.E4E36ED0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I have used the file scripting object =
in my=20
application.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>What do I need to include in my =
installation=20
routine to make sure that all files required are installed for the=20
user?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Sincerely</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Stephen</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0006_01C8821A.E4E36ED0--

Re: file scripting object by Fred

Fred
Sun Mar 09 14:42:17 CDT 2008

Since the file scripting is probably included with the OS, you really
shouldn't be installing anything. What you're more likely to run into is
that file scripting has been disabled by the system administrator or is
simply not even allowed within their environment.

--
Fred
Microsoft Visual FoxPro MVP


"Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
I have used the file scripting object in my application.

What do I need to include in my installation routine to make sure that all
files required are installed for the user?

Sincerely

Stephen



Re: file scripting object by Stephen

Stephen
Sun Mar 09 16:23:52 CDT 2008

Thanks Fred - that's what I was afraid of - I think I may have to re-work
this.

Sincerely

Stephen

"Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
news:u3A5z1hgIHA.5260@TK2MSFTNGP03.phx.gbl...
> Since the file scripting is probably included with the OS, you really
> shouldn't be installing anything. What you're more likely to run into is
> that file scripting has been disabled by the system administrator or is
> simply not even allowed within their environment.
>
> --
> Fred
> Microsoft Visual FoxPro MVP
>
>
> "Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
> news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
> I have used the file scripting object in my application.
>
> What do I need to include in my installation routine to make sure that all
> files required are installed for the user?
>
> Sincerely
>
> Stephen
>
>



Re: file scripting object by Paul

Paul
Wed Mar 12 16:53:22 CDT 2008

How does one enable or disable file scripting?

What does it mean "not allowed in their environment"?

Is there an easy test for these conditions?



"Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
news:u3A5z1hgIHA.5260@TK2MSFTNGP03.phx.gbl...
> Since the file scripting is probably included with the OS, you really
> shouldn't be installing anything. What you're more likely to run into is
> that file scripting has been disabled by the system administrator or is
> simply not even allowed within their environment.
>
> --
> Fred
> Microsoft Visual FoxPro MVP
>
>
> "Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
> news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
> I have used the file scripting object in my application.
>
> What do I need to include in my installation routine to make sure that all
> files required are installed for the user?
>
> Sincerely
>
> Stephen
>
>



Re: file scripting object by Fred

Fred
Wed Mar 12 20:33:37 CDT 2008

"not allowed" means the system administrator has either uninstalled, set up
a system policy to disable it, or in general just doesn't want it on their
systems. I guess you could check if it's installed, but that still won't
tell you if there's a system policy that will prevent if from working.

Try to create an object for it and if it fails, oh well.

--
Fred
Microsoft Visual FoxPro MVP


"Paul Pedersen" <nospam@no.spam> wrote in message
news:OwQa5tIhIHA.5160@TK2MSFTNGP05.phx.gbl...
> How does one enable or disable file scripting?
>
> What does it mean "not allowed in their environment"?
>
> Is there an easy test for these conditions?
>
>
>
> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
> news:u3A5z1hgIHA.5260@TK2MSFTNGP03.phx.gbl...
>> Since the file scripting is probably included with the OS, you really
>> shouldn't be installing anything. What you're more likely to run into is
>> that file scripting has been disabled by the system administrator or is
>> simply not even allowed within their environment.
>>
>> --
>> Fred
>> Microsoft Visual FoxPro MVP
>>
>>
>> "Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
>> news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
>> I have used the file scripting object in my application.
>>
>> What do I need to include in my installation routine to make sure that
>> all files required are installed for the user?
>>
>> Sincerely
>>
>> Stephen
>>
>>
>
>



Re: file scripting object by Paul

Paul
Thu Mar 13 11:19:38 CDT 2008

Thanks.

I asked because I had just run into such a case, where my app couldn't
create the file system object. Somehow, scrrun.dll had gotten unregistered.
I re-registered it, and it worked fine.

I was just wondering how common that situation would be, whether I should
consider building re-registering capability into my application, or even
putting scrrun.dll in the installer. I'd prefer not to do the latter,
because I don't know which OS takes which version of the dll, etc.




"Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
news:e8B4GoKhIHA.4740@TK2MSFTNGP05.phx.gbl...
> "not allowed" means the system administrator has either uninstalled, set
> up a system policy to disable it, or in general just doesn't want it on
> their systems. I guess you could check if it's installed, but that still
> won't tell you if there's a system policy that will prevent if from
> working.
>
> Try to create an object for it and if it fails, oh well.
>
> --
> Fred
> Microsoft Visual FoxPro MVP
>
>
> "Paul Pedersen" <nospam@no.spam> wrote in message
> news:OwQa5tIhIHA.5160@TK2MSFTNGP05.phx.gbl...
>> How does one enable or disable file scripting?
>>
>> What does it mean "not allowed in their environment"?
>>
>> Is there an easy test for these conditions?
>>
>>
>>
>> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
>> news:u3A5z1hgIHA.5260@TK2MSFTNGP03.phx.gbl...
>>> Since the file scripting is probably included with the OS, you really
>>> shouldn't be installing anything. What you're more likely to run into
>>> is that file scripting has been disabled by the system administrator or
>>> is simply not even allowed within their environment.
>>>
>>> --
>>> Fred
>>> Microsoft Visual FoxPro MVP
>>>
>>>
>>> "Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
>>> news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
>>> I have used the file scripting object in my application.
>>>
>>> What do I need to include in my installation routine to make sure that
>>> all files required are installed for the user?
>>>
>>> Sincerely
>>>
>>> Stephen
>>>
>>>
>>
>>
>
>



Re: file scripting object by Dan

Dan
Thu Mar 13 13:21:39 CDT 2008

A lot of admins disable WSH because of all the script viruses floating
around. You could be treading where you maybe shouldn't by re-enabling it.

The *smart* admins de-register the likely filename extensions the scripts
use instead, leaving the scripting object usable. But you really should talk
to them instead of just flaying open the machines they *think* are locked
down.

You wouldn't want *your* app to be a known virus-enabler. ;-)

Dan

Paul Pedersen wrote:
> Thanks.
>
> I asked because I had just run into such a case, where my app couldn't
> create the file system object. Somehow, scrrun.dll had gotten
> unregistered. I re-registered it, and it worked fine.
>
> I was just wondering how common that situation would be, whether I
> should consider building re-registering capability into my
> application, or even putting scrrun.dll in the installer. I'd prefer
> not to do the latter, because I don't know which OS takes which
> version of the dll, etc.
>
>
>
> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
> news:e8B4GoKhIHA.4740@TK2MSFTNGP05.phx.gbl...
>> "not allowed" means the system administrator has either uninstalled,
>> set up a system policy to disable it, or in general just doesn't
>> want it on their systems. I guess you could check if it's
>> installed, but that still won't tell you if there's a system policy
>> that will prevent if from working.
>>
>> Try to create an object for it and if it fails, oh well.
>>
>> --
>> Fred
>> Microsoft Visual FoxPro MVP
>>
>>
>> "Paul Pedersen" <nospam@no.spam> wrote in message
>> news:OwQa5tIhIHA.5160@TK2MSFTNGP05.phx.gbl...
>>> How does one enable or disable file scripting?
>>>
>>> What does it mean "not allowed in their environment"?
>>>
>>> Is there an easy test for these conditions?
>>>
>>>
>>>
>>> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
>>> news:u3A5z1hgIHA.5260@TK2MSFTNGP03.phx.gbl...
>>>> Since the file scripting is probably included with the OS, you
>>>> really shouldn't be installing anything. What you're more likely
>>>> to run into is that file scripting has been disabled by the system
>>>> administrator or is simply not even allowed within their
>>>> environment. --
>>>> Fred
>>>> Microsoft Visual FoxPro MVP
>>>>
>>>>
>>>> "Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
>>>> news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
>>>> I have used the file scripting object in my application.
>>>>
>>>> What do I need to include in my installation routine to make sure
>>>> that all files required are installed for the user?
>>>>
>>>> Sincerely
>>>>
>>>> Stephen



Re: file scripting object by Paul

Paul
Thu Mar 13 18:51:27 CDT 2008

I wouldn't want my app to be a known crasher either, which is what will
happen in that case now.

I guess I'll just have to check to see whether it works first, and if not,
notify the user and tell him to get whoever broke scripting to fix it again.

Unfortunately, that won't always be possible, as in the case I just
experienced. The user never heard of scripting, had no idea it was disabled,
had no one to go to about the problem except me, etc. If I'm not around,
which I won't be most of the time, in cases like that the app simply won't
work. And guess who will take the blame.



"Dan Freeman" <spam@microsoft.com> wrote in message
news:Ofr%23VcThIHA.5780@TK2MSFTNGP06.phx.gbl...
>A lot of admins disable WSH because of all the script viruses floating
>around. You could be treading where you maybe shouldn't by re-enabling it.
>
> The *smart* admins de-register the likely filename extensions the scripts
> use instead, leaving the scripting object usable. But you really should
> talk to them instead of just flaying open the machines they *think* are
> locked down.
>
> You wouldn't want *your* app to be a known virus-enabler. ;-)
>
> Dan
>
> Paul Pedersen wrote:
>> Thanks.
>>
>> I asked because I had just run into such a case, where my app couldn't
>> create the file system object. Somehow, scrrun.dll had gotten
>> unregistered. I re-registered it, and it worked fine.
>>
>> I was just wondering how common that situation would be, whether I
>> should consider building re-registering capability into my
>> application, or even putting scrrun.dll in the installer. I'd prefer
>> not to do the latter, because I don't know which OS takes which
>> version of the dll, etc.
>>
>>
>>
>> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
>> news:e8B4GoKhIHA.4740@TK2MSFTNGP05.phx.gbl...
>>> "not allowed" means the system administrator has either uninstalled,
>>> set up a system policy to disable it, or in general just doesn't
>>> want it on their systems. I guess you could check if it's
>>> installed, but that still won't tell you if there's a system policy
>>> that will prevent if from working.
>>>
>>> Try to create an object for it and if it fails, oh well.
>>>
>>> --
>>> Fred
>>> Microsoft Visual FoxPro MVP
>>>
>>>
>>> "Paul Pedersen" <nospam@no.spam> wrote in message
>>> news:OwQa5tIhIHA.5160@TK2MSFTNGP05.phx.gbl...
>>>> How does one enable or disable file scripting?
>>>>
>>>> What does it mean "not allowed in their environment"?
>>>>
>>>> Is there an easy test for these conditions?
>>>>
>>>>
>>>>
>>>> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
>>>> news:u3A5z1hgIHA.5260@TK2MSFTNGP03.phx.gbl...
>>>>> Since the file scripting is probably included with the OS, you
>>>>> really shouldn't be installing anything. What you're more likely
>>>>> to run into is that file scripting has been disabled by the system
>>>>> administrator or is simply not even allowed within their
>>>>> environment. --
>>>>> Fred
>>>>> Microsoft Visual FoxPro MVP
>>>>>
>>>>>
>>>>> "Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
>>>>> news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
>>>>> I have used the file scripting object in my application.
>>>>>
>>>>> What do I need to include in my installation routine to make sure
>>>>> that all files required are installed for the user?
>>>>>
>>>>> Sincerely
>>>>>
>>>>> Stephen
>
>



Re: file scripting object by Dan

Dan
Fri Mar 14 13:57:32 CDT 2008

Sounds to me like you have a requirements issue.

We publish our requirements. Don't you? ;-)

If your app prints, what do you do if they don't have a printer installed?
Pick one out of the air and install it? <g>

Dan


Paul Pedersen wrote:
> I wouldn't want my app to be a known crasher either, which is what
> will happen in that case now.
>
> I guess I'll just have to check to see whether it works first, and if
> not, notify the user and tell him to get whoever broke scripting to
> fix it again.
> Unfortunately, that won't always be possible, as in the case I just
> experienced. The user never heard of scripting, had no idea it was
> disabled, had no one to go to about the problem except me, etc. If
> I'm not around, which I won't be most of the time, in cases like that
> the app simply won't work. And guess who will take the blame.
>
>
>
> "Dan Freeman" <spam@microsoft.com> wrote in message
> news:Ofr%23VcThIHA.5780@TK2MSFTNGP06.phx.gbl...
>> A lot of admins disable WSH because of all the script viruses
>> floating around. You could be treading where you maybe shouldn't by
>> re-enabling it. The *smart* admins de-register the likely filename
>> extensions the
>> scripts use instead, leaving the scripting object usable. But you
>> really should talk to them instead of just flaying open the machines
>> they *think* are locked down.
>>
>> You wouldn't want *your* app to be a known virus-enabler. ;-)
>>
>> Dan
>>
>> Paul Pedersen wrote:
>>> Thanks.
>>>
>>> I asked because I had just run into such a case, where my app
>>> couldn't create the file system object. Somehow, scrrun.dll had
>>> gotten unregistered. I re-registered it, and it worked fine.
>>>
>>> I was just wondering how common that situation would be, whether I
>>> should consider building re-registering capability into my
>>> application, or even putting scrrun.dll in the installer. I'd prefer
>>> not to do the latter, because I don't know which OS takes which
>>> version of the dll, etc.
>>>
>>>
>>>
>>> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
>>> news:e8B4GoKhIHA.4740@TK2MSFTNGP05.phx.gbl...
>>>> "not allowed" means the system administrator has either
>>>> uninstalled, set up a system policy to disable it, or in general
>>>> just doesn't want it on their systems. I guess you could check if
>>>> it's installed, but that still won't tell you if there's a system
>>>> policy that will prevent if from working.
>>>>
>>>> Try to create an object for it and if it fails, oh well.
>>>>
>>>> --
>>>> Fred
>>>> Microsoft Visual FoxPro MVP
>>>>
>>>>
>>>> "Paul Pedersen" <nospam@no.spam> wrote in message
>>>> news:OwQa5tIhIHA.5160@TK2MSFTNGP05.phx.gbl...
>>>>> How does one enable or disable file scripting?
>>>>>
>>>>> What does it mean "not allowed in their environment"?
>>>>>
>>>>> Is there an easy test for these conditions?
>>>>>
>>>>>
>>>>>
>>>>> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
>>>>> news:u3A5z1hgIHA.5260@TK2MSFTNGP03.phx.gbl...
>>>>>> Since the file scripting is probably included with the OS, you
>>>>>> really shouldn't be installing anything. What you're more likely
>>>>>> to run into is that file scripting has been disabled by the
>>>>>> system administrator or is simply not even allowed within their
>>>>>> environment. --
>>>>>> Fred
>>>>>> Microsoft Visual FoxPro MVP
>>>>>>
>>>>>>
>>>>>> "Stephen Ibbs" <stephen@ibbs.org.uk> wrote in message
>>>>>> news:uFN8krhgIHA.4684@TK2MSFTNGP06.phx.gbl...
>>>>>> I have used the file scripting object in my application.
>>>>>>
>>>>>> What do I need to include in my installation routine to make sure
>>>>>> that all files required are installed for the user?
>>>>>>
>>>>>> Sincerely
>>>>>>
>>>>>> Stephen