Printable View
When creating a VB app using any control, such as Sheridan combobox, how do create an exe and have it run on another computer. I know you can package and create an install, but how to just compile and create an exe, then copy and place the controls .OCX in the destination PC's windows\system folder. When running the app, it tells me that some of the controls .OCX are not properly registered. How to do that 'registering', I thought it happened automaticaly.
Any help is welcome,
Thanks,
Patrick
You can either register the controls by creating an install program (preferred) or by running regsvr32 on the control.
Just to get a better grip on what I'm doing, I would like to understand and be able to do it without the VB setup method.
I have tried to register the control's OCX file using the following method :
REGSRV32 SSDW3BO.OCX
I keep receiving the following error msg :
Load library("C:\Windows\System\SSDW3BO.OCX") failed.
GetLastError returns : 0x0000001f.
I think that according the Sheridan documents, I have copied all needed files, but I can be wrong.
Thanks for help,
Patrick
It might have something to do with licensing of the control.
I have the same problem with another OCX, infact I receive the same message.
The SETUP create an unistall file in the same directory of the application. See it!
I think that the problem is in S.O. W95. Infact, I have installed my applicatiI on on a PC with a Winndows95 FAT16, while the control used for my application is for a FAT32. I don't know if is this the real problem, but i reinstall Windows for FAT32. Tell me about at [email protected]
Felice
I have the same problem with another OCX, infact I receive the same message.
The SETUP create an unistall file in the same directory of the application. See it!
I think that the problem is in S.O. W95. Infact, I have installed my applicatiI on a PC with a Winndows95 FAT16, while the control used for my application is for a FAT32. I don't know if is this the real problem, but I reinstall Windows for FAT32. Tell me about at [email protected]
Felice
u ppl are not specifying the right path where the dll or ocx file lies