Hello all,
I've had an access 2007 runtime app out since October. So far, it's been a
very stable download / install, regardless of whether they have widows xp,
or vista. I've had 2 instances recently where, upon first installing my
software, then attempting to launch, the user has received the dreaded Error
429 Active X can't create object.
I'm really only using 4 .dll's / .ocx's:
-------------------------------------
RedRegistration 3.dll (used as a call for the user name / company name, to
see if their product key is valid)
ipworks4.dll (proprietary e-mail add-in for direct e-mailing in the program)
easymail.dll (proprietary e-mail add-in for direct e-mailing in the
program)
Then finally, MSCOMCTL.OCX (to enable the treeview control)
---------------------------------------
That's all the dll's I have. Now, in my installation, I had all 4 of the
above set to check the version and only overwrite if present version is
older. Both user's that reported the active x error immediately upon
installing then launching, had windows vista.
Since then, I made a test, and set the above 4 files to Always Overwrite,
re-compiled, and uploaded. Well, this fixed the problem. The one user having
the trouble did have a MSCOMCTL.OCX on their computer, and the file date was
a couple years newer, yet the file size was the same. I'm suspecting it was
MSCOMCTL.OCX. Question is, why? My solution of having my installation
always overwrite MSCOMCTL.OCX seems to have fixed the problem, but I'd just
like to know why it would cause trouble in the first place, and if there are
dangers of having my install always overwrite. I guess it could break
another app they have, etc.
Thanks!
Andy
I've had an access 2007 runtime app out since October. So far, it's been a
very stable download / install, regardless of whether they have widows xp,
or vista. I've had 2 instances recently where, upon first installing my
software, then attempting to launch, the user has received the dreaded Error
429 Active X can't create object.
I'm really only using 4 .dll's / .ocx's:
-------------------------------------
RedRegistration 3.dll (used as a call for the user name / company name, to
see if their product key is valid)
ipworks4.dll (proprietary e-mail add-in for direct e-mailing in the program)
easymail.dll (proprietary e-mail add-in for direct e-mailing in the
program)
Then finally, MSCOMCTL.OCX (to enable the treeview control)
---------------------------------------
That's all the dll's I have. Now, in my installation, I had all 4 of the
above set to check the version and only overwrite if present version is
older. Both user's that reported the active x error immediately upon
installing then launching, had windows vista.
Since then, I made a test, and set the above 4 files to Always Overwrite,
re-compiled, and uploaded. Well, this fixed the problem. The one user having
the trouble did have a MSCOMCTL.OCX on their computer, and the file date was
a couple years newer, yet the file size was the same. I'm suspecting it was
MSCOMCTL.OCX. Question is, why? My solution of having my installation
always overwrite MSCOMCTL.OCX seems to have fixed the problem, but I'd just
like to know why it would cause trouble in the first place, and if there are
dangers of having my install always overwrite. I guess it could break
another app they have, etc.
Thanks!
Andy