AC2002: Error 429 on XP SP1 - never happened on other installs !

  • Thread starter Thread starter Björn Comhaire
  • Start date Start date
B

Björn Comhaire

Hi,

I have created a commercial application in Access 2000 some 4-5 years ago. I
installed the system with about 15 clients and never had any problems.

Now one of my clients tried to install the package on a new WinXP SP1
computer (with MS OF2000 on it) and as soon as they start up the application
they get a runtime error 429 (ActiveX).
The first thing I do when the program is run is check to see if the program
is properly registered and this is done using a text file file with the
registration info scrambled inside it. the textfile is opened using
"Scripting.FileSystemObjectobject" (fso). Since I thought that this might be
the cause of the problem I installed the scripting engine separately on this
PC, but no joy.

The version of my program they have was compiled on a Win98 computer at the
time, could this be the cause of the troubles ? I have the software running
on some other WinXP computers without problems (well not problems that
couldn't be solved easily).

Thx for the help,
Björn
 
Was it installed using an installation program?

Is the activex control that it is referring to available on the XP machine?
 
Hi,

Yes the program was installed using the Access2000 developer edition
installer + runtime (which I had to install manually since AC2000 was on the
PC already.
The main problem is that the error message doesn't specify which OCX wasn't
installed correctly. Hence my reinstalling of the scripting libraries...

Björn
 
Which version of access runs when the app is opened?
I believe, but could be wrong, that you have to tell it explicitly which
version to use otherwise the full version will open.
 
Well I tried both, running it with the full version and running it with the
runtime version which I installed separately in a different directory.
AC2000 in both cases.

Björn
 
I'm new to this so I'm running out of ideas . . . My understanding is that
that error 429 is some kind of problem with a missing DLL (or OCX), not
registered DLL, corrupt DLL, or rights issue accessing that DLL.

Do you get the same problem when trying to run the app when logged on as
administrator?
Have you tried manually re-copying all the necessary ActiveX controls on to
the machine?
Did the other XP machines have full Off2000 installed?
 
Björn Comhaire said:
Now one of my clients tried to install the package on a new WinXP SP1
computer (with MS OF2000 on it) and as soon as they start up the application
they get a runtime error 429 (ActiveX).
Click to expand...

You probably need to register the DAO dll using regsvr32. For example
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\
DAO360.DLL"

ACC2000: Error Message: ActiveX Component Can't Create Object
http://support.microsoft.com/support/kb/articles/q296/2/04.asp

Tiny
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top