🚀 go-pugleaf

In article <395a09f8$1_1@news.chariot.net.au>,
  "Darryl Sellwood" <darryl@newave.net.au> wrote:
> We have a program in which the main project interfaces with 4 dells
and 10
> user controls, all of them our work. The program has been running fine
on
> our development computers, but when we made a set-up program recently
and
> tried it on some test computers it wouldn't run. The errors that occur
are
> Error 429 "Cannot create ActiveX Component", and also Error 429 "You
do not
> have an appropriate licence to use this functionality". Before we
compiled
> the project group, we ticked the "Require License Key" checkbox in the
> project options dialog for all of the user controls. We then used the
> Package and Deployment Wizard to create the set-up program for the
project,
> and added the .VAL files in at the appropriate time. A quick check in
the
> registries of the test machines after installation shows that the
license
> keys are there, and that the user objects and dells are registered
> correctly.
>
> We installed Win, I.E. and VIBE + SPA with the project.  The project
worked.
> For a test  we installed the install package then tried running the
program
> but it still had the same error.
>
> The VB6Cli.exe was install but it doesn't help, which was suggested in
> Q194751 MS Knowledge base.
>
> What are we missing here? Or is there any work around available?
>
> Also if there is anyone in Adelaide, South Australia who could help us
> hands-on, we'd be very interested to hear from you.
>
> Please reply to darryl@accede.com.au
>
> Thank you,
>
> Darryl Sellwood

I ran into a similar problem recently.  I don't know if this has
anything to do with what you're getting, but here's what it was for me:

I downloaded and installed the (non-distributable) demo version of an
OCX control, then put it in my project to try it out.  It worked well,
so I purchased the registered version and installed it.  Everything
worked great on the development machine, but I got the 429 "appropriate
license" error on all user installs.

It turns out that both the demo and the registered versions of the OCX
were still on my computer.  Somehow or other, the Package & Deployment
Wizard was picking up the demo version.  The solution turned out to be
merely deleting all copies of the demo version, then repackaging the
project.  After that, everything was fine.


Sent via Deja.com http://www.deja.com/
Before you buy.