Infragistics controls and the accont Docking Container

Infragistics controls and the accont Docking Container

Anonymous
Not applicable
224 Views
1 Reply
Message 1 of 2

Infragistics controls and the accont Docking Container

Anonymous
Not applicable
Has anyone used Infragistics UltraGrid and/or ActiveThreed with the
accont.arx Docking Container? We believe that we are running into a
licensing problem on non development machines. Since our ocx (which uses
Infragistics controls) is passed to accont at run time, we believe that
UltraGrid is seeing its creation as a design time operation and refusing to
be created on any machine but a development machine.

The strange thing is that we get no error messages from UltraGrid. accont
simply returns an error message that it can't load our ocx. Another oddity
is that in one of our test cases it actually works from time to time (one
would think that it would never load on a non-developer licensed machine).

Most importantly, does anyone have a work around for this issue?

Regards,
Donald F. Sanborn
dsanborn@uniqsol.com
0 Likes
225 Views
1 Reply
Reply (1)
Message 2 of 2

Anonymous
Not applicable
I had the same problem when I incorporated licensing into my
ProPack.ocx (although I am not using the controls you mentioned). The
only fix I found was to remove the license key requirement.

--
http://www.acadx.com
Win an autographed copy of
"Mastering AutoCAD 2000 Objects"
by Dietmar Rudolph

"dsanborn" wrote in message
news:C1CB6ECD933862C7E754FCB523962083@in.WebX.maYIadrTaRb...
> Has anyone used Infragistics UltraGrid and/or ActiveThreed with the
> accont.arx Docking Container? We believe that we are running into a
> licensing problem on non development machines. Since our ocx (which
uses
> Infragistics controls) is passed to accont at run time, we believe
that
> UltraGrid is seeing its creation as a design time operation and
refusing to
> be created on any machine but a development machine.
>
> The strange thing is that we get no error messages from UltraGrid.
accont
> simply returns an error message that it can't load our ocx. Another
oddity
> is that in one of our test cases it actually works from time to time
(one
> would think that it would never load on a non-developer licensed
machine).
>
> Most importantly, does anyone have a work around for this issue?
>
> Regards,
> Donald F. Sanborn
> dsanborn@uniqsol.com
>
0 Likes