"ActiveX component can't create object"
 

When using CreateObject("Scripting.FileSystemObject") I get this error. It
works on one account on my computer but not on the other. I have done a
clean reload of Office 2003 to no avail.

"ActiveX component can't create object"
 

William,
Scripting can be disabled by Windows permissions/policies. Check those for
the user account that fails compared to the one that works.

However, what do you need the FSO for ?
You can probably avoid it anyway.

NickHK

"William wilborn" <William wrote in
message ...
When using CreateObject("Scripting.FileSystemObject") I get this error.
It
works on one account on my computer but not on the other. I have done a
clean reload of Office 2003 to no avail.

"ActiveX component can't create object"
 

"NickHK" wrote:

William,
Scripting can be disabled by Windows permissions/policies. Check those for
the user account that fails compared to the one that works.

However, what do you need the FSO for ?
You can probably avoid it anyway.

NickHK

"William wilborn" <William wrote in
message ...
When using CreateObject("Scripting.FileSystemObject") I get this error.
It
works on one account on my computer but not on the other. I have done a
clean reload of Office 2003 to no avail.


I didn't make it clear I guess, I am working with Excel 2003 macros. It is a large user gui for my model.

"ActiveX component can't create object"
 

Still, you can (probably) remove the need for the Scripting component
completely anyway.

NickHK

"William wilborn" wrote in
message ...


"NickHK" wrote:

William,
Scripting can be disabled by Windows permissions/policies. Check those
for
the user account that fails compared to the one that works.

However, what do you need the FSO for ?
You can probably avoid it anyway.

NickHK

"William wilborn" <William wrote in
message ...
When using CreateObject("Scripting.FileSystemObject") I get this
error.
It
works on one account on my computer but not on the other. I have done
a
clean reload of Office 2003 to no avail.


I didn't make it clear I guess, I am working with Excel 2003 macros. It
is a large user gui for my model.