Program installation on new machines

[NitoNito]

Hi.
I need a help on installation of programs that i create onto a new machine. I had this problem when after installation on a new machine asks me for an active X control specifically MSADOC.OCX. I have my own .dlls files that i create and register them during that program installation. I have no active X controls to register.

The program install well and executes in the machine that i used to create the program.

The funny thing is that I have to install Visual Basic 6(The one i used to program) for it to run. And it actually runs well. Now, i look this OCX file in the location c:\WINDOWS\system32 and i find it there.

I then uninstall this VB and i just take this OCX file and copy it in that location and still doesnt run.

Q.
How can i make my programs independent of the program used to create these softwares specifically VBA 6.

[Hack]

Moved to Application Deployment

[randem]

You need to create a proper installation and it will handle those problems. Your problem seems to stem from not having all the dependencies that your app needs.

What installer are your using?

[NitoNito]

I am using inno setup and i do add my files to be registered and they are actually registered. What is to make it dependent because no other activex and dll am using except the one that i register using inno setup

please help.
thanks in advance.

[randem]

How did you find the dependencies that you need in the first place?

Post your script.

[tatkosmurff]

VB 6.0 is not an application its an environment. With your source editor the istallation includes a lot of libraries, tool etc.

Your program has two parts the ones you create :
*.exe, *.ocx, *.Dll ....

and the once you use in your application- these are the components
form the environment. For example adding a list view control to your
GUI means that an OCX component is assigned as part of your application.
When you want to run your application all components assigned to it have to be available.

Now the second part can contain some components you haven't added at
design time, like couple of system dlls, dlls required from the aciveX you used.
Thus the setup generator program automatically searches your project or exe
and loads a list of all dependancies to your project. You don't have to add them manually unless you know exactly what system resources you use.

In your case the component that is missing is the ado control(i suppose). You may have forgotten it somwhere in your GUI or you may have forgotten to remove the component from your project components list, in both cases No installation of VB is needed
the easyest way to solve that is to register the ocx manually
just find the file in your PCs windows\system dir copy it to the
new PCs windows\system dir then call from the run menu ->regsvr32 c:\WINDOWS\system32\MSADOC.OCX

this will do it without installing and uninstalling VB
The best is to check your code again and generate correct setup

[tatkosmurff]

VB 6.0 is not an application its an environment. With your source editor the istallation includes a lot of libraries, tool etc.

Your program has two parts the ones you create :
*.exe, *.ocx, *.Dll ....

and the once you use in your application these are the components
form the environment you use. For example adding a list view control to your
GUI means that an OCX component is assigned as part of your application.
When you want to rub your application all components assignet to it have to be available.

Now the second part can contain some components you haven't added on
design time, like couple of system dlls, dlls required from the aciveX you used
thus the setup generator program automatically searches your project or exe
and loads a list of all dependancies to your project. You don't have to add them manually unless you know exactly what system resources you use.

In your case the component that is missing is the ado control. You may have forgotten somwhere in your GUI or you may have forgotten to remove the component from your project components list, in both cases No installation of VB is needed
the easyest way to solve that is to register the ocx manually
just find the file in your PCs windows\system dir copy it to the
new PCs windows\system dir then call in the run menu ->regsvr32 c:\WINDOWS\system32\MSADOC.OCX

this will do it without installing and uninstalling VB
The best is to check your code again and generate correct setup