CreateObject("Scripting.FileSystemObject") stopped working
 

I have a script I have been using regularly which includes the lines

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

Today the second line is suddenly giving me Automation Error, Library Not
Registered.

Since this used to work and the Library Microsoft Scripting Runtime IS
registered I am at a loss to understand what is going on.

I am hoping the problem is unrelated to a heap of Office updates that XP
installed for me today.

Andrew

CreateObject("Scripting.FileSystemObject") stopped working
 

Try reregistering the drive:\Windows\System32\scrrun.dll file.

--
Eric Legault (Outlook MVP, MCDBA, MCTS: Messaging & Collaboration)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"Andrew Hall NZ" wrote:

I have a script I have been using regularly which includes the lines

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

Today the second line is suddenly giving me Automation Error, Library Not
Registered.

Since this used to work and the Library Microsoft Scripting Runtime IS
registered I am at a loss to understand what is going on.

I am hoping the problem is unrelated to a heap of Office updates that XP
installed for me today.

Andrew

CreateObject("Scripting.FileSystemObject") stopped working
 

Thanks, that did the trick, should have thought of it myself

Andrew

"Eric Legault [MVP - Outlook]" wrote:

Try reregistering the drive:\Windows\System32\scrrun.dll file.

--
Eric Legault (Outlook MVP, MCDBA, MCTS: Messaging & Collaboration)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"Andrew Hall NZ" wrote:

I have a script I have been using regularly which includes the lines

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

Today the second line is suddenly giving me Automation Error, Library Not
Registered.

Since this used to work and the Library Microsoft Scripting Runtime IS
registered I am at a loss to understand what is going on.

I am hoping the problem is unrelated to a heap of Office updates that XP
installed for me today.

Andrew