Visual Basic project scan

[alanK]

I just discovered that an OCX control included in my VB project was not detected by the SF VB project file scan.

The OCX was identified in an "Object" line in the .vbp file. Are there any circumstances where an OCX would not be picked up?

[Mark]

Hi,

Which version of Setup Factory are you using? What is the name of the OCX control that is not being picked up?

mark.

[alanK]

Version is 6.0.1.0 (from About screen)

line from vbp file is:

Object={B26F6243-4C7D-11D1-910E-00600807163F}#2.78#0; XCDZIP35.OCX

The OCX is registered and runs correctly on my machine - but was not included in SF file list

[alanK]

More info...

The OCX is not located in the C:\WINNT directory, but in an obscure user directory. However, the Registry correctly points to that location. I moved the OCX to C:\WINNT and re-registered it there (checking with Regedit that it was correctly done) - still not picked up by SF.

Created a new VB project and included just that OCX as a component - not picked up by SF.

I have other 3rd party DLL's and OCX's (eg. ActiveReports) in the main project, and these are detected correctly.

[Mark]

Hi,

It should not matter where the OCX is located. Perhaps you could send me a project file that uses the OCX and Setup Factory does not pick it up. That way I could analyze the way Setup Factory treats this entry.

Are you sure that the OCX is registered properly? Perhaps you could export the Registry key so I could add that to my registry.

Send the information to mark@indigorose.com

mark.

[Boredbert]

I am also having this problem with a product from Sheridan. Was there any resolution? Mine looks like this:

Object={8D650141-6025-11D1-BC40-0000C042AEC0}#3.0#0; ssdw3b32.ocx

Thanks,
Jason

[alanK]

Problem in my case was that the version on the OCX in the registry did not match the version in the VB project file. This is not SF's problem; it is a fault with the OCX when it registers itself.

SF ignores the OCX if the versions don't match. I have suggested that it should display an error or produce an exceptions report - not just ignore the problem.

You will have to manually add the OCX to your project.

[Darryl]

In the next update patch, there should be an error message generated if for some reason the file could not be added, but was referenced in the Visual Basic project file.