Hi,
I'm using merge modules for Crystal Reports XI in my product installation. They required to provide a license key as value to their PIDKEY in License module. Crystal is the part of my product install, that also uses PIDKEY in serial dll product validation. It means that when user sees UserRegistration Dialog, Serial number field is already populated with a value of Crystal PIDKEY.
I think that the scope of these PIDKEY values should be different and should not collide.
Is this a bug? or I should change the PIDKEY property name for one or another product. In this case how?
Thanks,
Andrei
Suggested Articles
Hi Andrei,
Indeed, the Crystal Reports license MSM uses a configurable Property whose name is identical to the PIDKEY WI Property (whose value represents the part of the Product ID entered by the user):
http://msdn2.microsoft.com/en-us/librar ... S.85).aspx
The workaround would be to use your own serial validation DLL and a new dialog similar to UserRegistrationDlg. The Property attached to the Masked Edit control on this new dialog will have a name different than PIDKEY.
Regards,
Ionut
Indeed, the Crystal Reports license MSM uses a configurable Property whose name is identical to the PIDKEY WI Property (whose value represents the part of the Product ID entered by the user):
http://msdn2.microsoft.com/en-us/librar ... S.85).aspx
The workaround would be to use your own serial validation DLL and a new dialog similar to UserRegistrationDlg. The Property attached to the Masked Edit control on this new dialog will have a name different than PIDKEY.
Regards,
Ionut