Re: Interesting activeX problem / solution
- From: "Terry Kreft" <terry.kreft@xxxxxxxxx>
- Date: Mon, 25 Feb 2008 12:04:51 -0000
Assuming no bugs, the reasons why it broke could be:-
1) Version branching
2) Mis-Dated file
Version branching is where for example a developer keeps source code in a
versioning repository (such as MS Sourcesafe) they develop along one branch
and then by accident or design go to an earlier version and start developing
again. In this way you can get two binaries with the same version numbers
which are different.
Mis-dated file can be caused by someone maliciously or foolishly forcing
their version of a file onto a system by changing the date.
By forcing an overwrite you are risking breaking software on peoples
machines. Indeed I have known an OS (Windows XP) be broken in this way.
--
Terry Kreft
"ARC" <PCESoft@xxxxxxxxxxxxxxx> wrote in message
news:6Ejwj.58648$Pv2.2791@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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:
-------------------------------------
RedRegistration3.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
.
- References:
- Interesting activeX problem / solution
- From: ARC
- Interesting activeX problem / solution
- Prev by Date: Re: preventing user to access/see/import/linking tables
- Next by Date: Re: SQL Problem
- Previous by thread: Interesting activeX problem / solution
- Next by thread: LE&M resource allocation objective
- Index(es):
Relevant Pages
|
