[MichaelBaker]

Hello all,

We have created a custom OCX control using Avax Vector Active X. The OCX is then referenced in a VB6 standard EXE project. In the application, the registered version of Avax Vector Active X is properly referenced.

On the developer machine, everything runs fine. On any other machine, we still get the nag screen.

What can I do in my installation to assure the nag screen does not come up for our client? In simpler terms, what do I need to include in my install to keep the nag screen off of our installed application?

Our client will be very unhappy seeing the nag screen.

Regards,
Bill

[Athanasios Gardos]

You have to distribute avax.ocx file that is in your developer machine. That file contains the information of the nag screen disappearance.

[MichaelBaker]

I have successfully created the install program. I get a registration error on these 3 files, however, during set up. The error is "DLLRegisterEntry point not found".

19 gvlib32.dll
20 avImageX.dll
21 avaxgrph.dll

Do these need to be registered during set up?

My app runs without error and without the nag screeen. It just doesn't draw anything.

Thanks for your help,
Bill Hojecki
Michael Baker Inc.

[Athanasios Gardos]

You have to just copy (without the use of regsvr32.exe program) those three files into the windows system directory (system32).