Hi,
The nag screen appears when the application is not licensed. There may be certain reasons for the license nag screen to appear on client machines:
1. Are you instantiating VSPrinter at run time? Please note, it is needed to embed the license key for ActiveX controls created at run time as explained in the following blog article:
http://our.componentone.com/2011/03/04/embedding-license-key-for-activex-controls-created-at-run-time/
Or, you may place an invisible VSPrinter control on Form designer. This would automatically embed the licensing info.
2. The issue may also be related to the distribution of wrong controls. We ship both a 32bit and 64bit version of our ActiveX controls. The 64bit controls are geared towards C++ developers as VB6 never went beyond 32bit.
With 64-bit versions of windows, the 32bit controls are stored in the C:\Windows\SysWow64 folder and the 64bit controls are stored in the C:\Windows\System32 folder. This is reverse of what seems logical but this is the way Microsoft has done it.
I would suggest try deploying the versions of the controls from the C:\Windows\SysWow64 folder along with your application and see if that resolves the issue. Below is a link with more information about registering the ActiveX controls.
http://our.componentone.com/2012/02/10/registration-of-64-bit-activex-controls/
3. There may be different versions of VSPrint8.ocx (on client machine) which do not match the version against which you compiled your application. Please make sure that the version for which you are observing the nag screen is the one against which you compile your application.
If you have access to the client machine, you may try scanning the hard drive to check if there are multiple copies of VSPrint8.ocx in it. If so, you need to remove the other versions and keep only the version against which your application is compiled.
In addition to this, you may want to go through the "License Nag on Client Machine" section in the following blog article:
http://our.componentone.com/2012/08/17/troubleshooting-activex-licensing/
If the problem still persists, please let me know how exactly are you distributing this application to your clients.
Thanks,
Pragati