Controls running in evaluation mode?

[OsmanUllah]

I am trying to distribute my MS Access Application that contains a couple ComponentWorks controls (cwinstr.ocx and cwanalysis.ocx). I am building the package using the Package & Deployment wizard. However, after installing the application on the applicable computer, when I run the application the CW controls are running evaluation mode.

I looked in the help file, and all it says is that the program does not contain the correct run-time license. Is this a file that I am supposed to distribute with the program?

Thanks,

Osman

[Chris Matthews]

Most ActiveX controls that are sold include licenses that are installed on the development machine and have to be embedded in any EXE or DLL that you distribute. Visual Basic and Visual C++ automatically include these licenses in the EXEs and DLLs that they build if you are using the ActiveX control on a dialog or form. I'm not sure how embedding the licenses would be done in a Microsoft Access database since it isn't compiled and linked into a binary. Consult Microsoft or MSDN for how to distribute an Access database that uses licensed ActiveX controls.

There is some information in our KB on similar problems with ATL projects in VC++ for which Microsoft had a solution 6155abe7bf57f862568a4006ee41d?OpenDocument>here. We also explain how to manually add these licenses when dynamically creating a control at run-time here.

Best Regards,

Chris Matthews
National Instruments

[OsmanUllah]

Thanks Chris for pointing me in the right direction. I'll refer to MSDN for my solution.

Thanks,

Osman

[OsmanUllah]

Chris,

Upon further investigation I have found that this only happens in Windows 98. I have no such problem in NT. Furthermore, it only happens when I open the application for the first time. I've loaded the application again and haven't gotten the message (even after rebooting). Does this mean that everything is OK, or are the controls running in demo mode and just not telling me?

Thanks,

Osman

[OsmanUllah]

Actually, the same thing is happening in Windows 2000. It gives the warning once, and then after that it doesn't give it again, even after rebooting.

[Chris Matthews]

No, you will continue to see the message until the licenses are detected. Again, I am not familiar with how Access does licensing, but it sounds like there may be some initialization order problem when first opening the database. If the eval messages go away, the license was detected though.

Chris