runtime error '429'

[Chris]

I have an access 2000 program that is running on sevral machines and
working fine.

On one machine XP, Office2K the program gives the error:
runtime error 429, Active x Component can't create object.

This error occurs on the line "Set Fso....."

Dim fso As New FileSystemObject
Set fso = CreateObject("Scripting.FileSystemObject")

I have tried an office Repair, office upgrade, Reinstalling office,

I have the the following references installed.
Visual Basic for Applications
Microsoft Access 9.0 for Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data objects 2.8 Library
Microsoft Scripting Runtime
Microsoft ActiveX Data Objects Recordset 2.8 Library
Microsoft Active X Plugin

I have tried the microsoft solution of running the 09regfix.exe
The file for the active x pluging plugin.ocx is in the correct folder.

Please help.

 

[Douglas J. Steele]

You've already instantiated the object when you used the New keyword.
However, you're far better off in VBA to not use the New keyword.

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

or

Dim fso As FileSystemObject
Set fso = New FileSystemObject

 

[Norman Yuan]

Better yet, do not use Scripting.FileSystem at all. There is nothing you can
do with Scripting.FileSystem object while VBA intrinsic file handling
function cannot do.

Scripting engine comes different versions with different version of Windows,
and it may be disabled by administrator on a strictly managed network for
security reason. Due to these reasons and possible others, use it may cause
some issue, as you now experiencing exactly. So, using VBA intrinsic file
handling functions is the ultimate solution in this case.

 

[dbahooker]

uh; i'd love some more information about why we're better off not
using the New keyword.

Is it faster to not use the New Keyword?

I use this all the time

Dim rst as new ADODB.recordset

is that not appropriate??