CreateObject("Scripting.FileSystemObject") Fails on some sta

Dave · Joined: 04 Oct 2007 Posts: 4

Hi

I wrote a little VB prog in which I create a "Scripting.FileSystemObject" object
this works perfectly on 99% of our workstations but on some
the CreateObject command fails????

Any idea what could cause this problem?
Could it be an outdate dll or ocx file?
How can I troubleshoot this problem?

Dim fs As Object
Set fs = CreateObject("Scripting.FileSystemObject")
...
...

thx in advance
Dave

Archived from group: microsoft>public>vb>controls

Al Reid · Joined: 04 Oct 2007 Posts: 230

"Dave" wrote in message @4ax.com...
> Hi
>
> I wrote a little VB prog in which I create a "Scripting.FileSystemObject" object
> this works perfectly on 99% of our workstations but on some
> the CreateObject command fails????
>
> Any idea what could cause this problem?
> Could it be an outdate dll or ocx file?
> How can I troubleshoot this problem?
>
>
> Dim fs As Object
> Set fs = CreateObject("Scripting.FileSystemObject")
> ..
> ..
>
>
> thx in advance
> Dave
>

Dave,

The best way would be to loose the Scripting.FileSystemObject and use native VB file handling.

--

Al Reid

Bob Butler · Joined: 04 Oct 2007 Posts: 2047

"Dave" wrote in message@4ax.com
> Hi
>
> I wrote a little VB prog in which I create a
> "Scripting.FileSystemObject" object this works perfectly on 99% of
> our workstations but on some the CreateObject command fails????
>
> Any idea what could cause this problem?
> Could it be an outdate dll or ocx file?
> How can I troubleshoot this problem?

It requires that scrrun.dll be installed on the system; in some
environments that file is specifically not allowed to prevent malicious
scripts to run. In your case it's probably just missing. As Al Reid
mentioned, your best bet is just to drop the FSO completely; compared to the
native VB commands (and an API call or two) it is slow, adds overhead and
makes your app susceptible to problems like this. There is nothing you need
it for.

--
Reply to the group so all can participate
VB.Net: "Fool me once..."

Dave · Joined: 04 Oct 2007 Posts: 4

Thx a lot Bob
scrrun.dll was indeed missing on the problemstations.
copying & registering the DLL fixed it

I will rewrite my source in native VB when I have some more time.

thx again

On Fri, 1 Apr 2005 05:47:30 -0800, "Bob Butler" wrote:

>"Dave" wrote in message
>@4ax.com
>> Hi
>>
>> I wrote a little VB prog in which I create a
>> "Scripting.FileSystemObject" object this works perfectly on 99% of
>> our workstations but on some the CreateObject command fails????
>>
>> Any idea what could cause this problem?
>> Could it be an outdate dll or ocx file?
>> How can I troubleshoot this problem?
>
>It requires that scrrun.dll be installed on the system; in some
>environments that file is specifically not allowed to prevent malicious
>scripts to run. In your case it's probably just missing. As Al Reid
>mentioned, your best bet is just to drop the FSO completely; compared to the
>native VB commands (and an API call or two) it is slow, adds overhead and
>makes your app susceptible to problems like this. There is nothing you need
>it for.

Why can't create Excel.Application object using CreateObject Hi, there, I try to create an object using CreateObject function, I got "nothing" from the return variable without any error messages, but It works well on another computer, we have the same environment same references

Why no love for Scripting.FileSystemObject? In a very recent thread regarding the determination of folder existence, is was suggested that "scripting is not the best way to go" and stated that FSO is "execrable". Is there a technical reason for this anti-FSO sentiment, or is it a purist's stance?

FileSystemObject For standalone VB6 program, do I use the to access the files? or FSO is only for ASP? -- > There is no answer. > There has not been an answer. > There will not be an answer. > That IS the answer! > And I am screwed. > Deadline was due ye

FileSystemObject folder length Hello, I am wondering if there is a limit on how long a folder path can be for the I am trying to copy a file into a folder structure. and getting an error. my path is longer than 256 chars. and this seems to be the problem. the path i

Error when using FileSystemObject.Move I am using the FSO in my program and everything is working fine until I try to use the Move command as follows: fs.MoveFile strFileOld, strFileNew Then I get the "Permission Denied" error. Then when I check file attributes, there are no restrictions. Plea