MFC, Q147740 CWnd work-around doesn't work with control that uses lic file

Q147740 CWnd work-around doesn't work with control that uses lic file

Author	Message
Mr. Idi #1 / 5	Q147740 CWnd work-around doesn't work with control that uses lic file Ok, I have my MFC application working just ducky with the OCX control I need to use. I put it on another system, and it no longer works. (Fails in the OnCreate() event, when I call the Control's Create() function.) If I distribute the lic file for the OCX, it works. While I'm sure our customers wouldn't mind getting the development licence for the control, the company that we purchased it from just might. <G> Help! Now what do I do? PI
Tue, 11 Jul 2000 03:00:00 GMT

Alexander Galki #2 / 5	Q147740 CWnd work-around doesn't work with control that uses lic file Quote: >Ok, I have my MFC application working just ducky with the OCX control >I need to use. I put it on another system, and it no longer works. >(Fails in the OnCreate() event, when I call the Control's Create() >function.) If I distribute the lic file for the OCX, it works. >While I'm sure our customers wouldn't mind getting the development >licence for the control, the company that we purchased it from just >might. <G> >Help! Now what do I do? > PI .lic file is design time license which is needed only during design time when you embed control in third party container. You MAY NOT distribute .lic file with the control. When you compile your application that uses the control you must provide runtime license. Runtime license is implemented as BSTR key which is last parameter in CWnd::CreateControl and that you must supply to be able to create control. Alexander Galkin Software Engineer Zebra Pushware Solutions, Inc. WWW: http://www.infopager.com
Tue, 11 Jul 2000 03:00:00 GMT

MCS #3 / 5	Q147740 CWnd work-around doesn't work with control that uses lic file Yes ocx controls use licensing to prevent unwarrented use. Basically licenses are of two types 1. design mode lic 2. run mode lic Generally once you buy a control the runtime license is redistributable but not design mode lic. so that your clients can run your application but not use the control in their application. So what you need to do is supply and install the run mode license with your control. for more clarification contact the control vendor. -- ---------------------------------------------------------------------------- Raejsh Parikh - Microsoft Certified Solution Developer ---------------------------------------------------------------------------- Quote: >Ok, I have my MFC application working just ducky with the OCX control >I need to use. I put it on another system, and it no longer works. >(Fails in the OnCreate() event, when I call the Control's Create() >function.) If I distribute the lic file for the OCX, it works. >While I'm sure our customers wouldn't mind getting the development >licence for the control, the company that we purchased it from just >might. <G> >Help! Now what do I do? > PI
Tue, 11 Jul 2000 03:00:00 GMT

Mr. Idi #4 / 5	Q147740 CWnd work-around doesn't work with control that uses lic file On Fri, 23 Jan 1998 11:57:46 +0200, "Alexander Galkin" Quote: >file with the control. When you compile your application that uses the >control you must provide runtime license. Runtime license is implemented as >BSTR key which is last parameter in CWnd::CreateControl and that you must >supply to be able to create control. BSTR key did it. Thanks guys. PI
Thu, 13 Jul 2000 03:00:00 GMT

Mr. Idi #5 / 5	Q147740 CWnd work-around doesn't work with control that uses lic file On Fri, 23 Jan 1998 17:01:05 +0530, "Rajesh Parikh (MCSD)" Quote: >So what you need to do is supply and install the run mode license with your >control. >for more clarification contact the control vendor. I'm out of the weeds (as far as this project, and this control), but is there an easy way to get the BSTR runtime license key? I never need to care about this in VB. How does VB get it? PI P.S. Thanks for the reply, it helped!
Thu, 13 Jul 2000 03:00:00 GMT

Page 1 of 1

[ 5 post ]