I did a VB program that may work with a third party ocx control
I need to install my program  with or without ocx following the customer
request.
Of course when I try to run my program without ocx, program generates
run-time error 339 that I can't manage.
I can't registry the ocx module when my customer dosen't want to buy it
because ocx needs to license.

How can I trap the error and continue my application?

Thanks to all
Erik

You should never open a form with the control on it if the control is not
registsered... and you should never in any function that can be called when
the control is not there use any types or constants from the OCX type
library.

VB is not very tolerant of using forms or functions that contain things from
references that do not exist.

Michael