>I have been reading up on manifests. Thanks for the suggestion - it looks like this is the way to go.
>
>I have several questions - perhaps you know the answers to some of them?
>
>1: My application has a small program goRun.exe that calls an APP. If I call the manifest file goRun.exe.manifest, will that be good for the OCXs used in the APP, or do I need a manifest for the APP as well. Perhaps "MyApp.APP.manifest"?

Only EXE can use a manifest.

>
>2: If goRun.exe calls another exe (goRun2.exe), does goRun2.exe need a manifest file as well, or does it "inherit" the initial one.

It depends on how the second EXE is called.

>
>3: When my application gets installed on the F: drive, I have been running a second install file on each user's PC that registers the controls on their computer. With a manifest file, I guess that this would not be needed anymore - a shortcut to the EXE on the network drive would work correctly?

Theoretically, yes but I'm not a big fan of running applications of the network drives. I prefer to run them from the local copy.

>
>4. What about files that get installed under Common files, for example, Crystal reports. At the moment I install these on each user's PC, and register them on each PC, example:
> Register Library $COMMONFILES$\Crystal Decisions\2.0\bin\crqe.dll
>
>I am inclined to leave this alone, as so far it works Would it be better to bring these into the manifest instead of doing the registration?
>
>I am just starting off with manifests, so I will be doing a lot of experiments. Any other tips?
>