Type Libraries Are They For Everyone

Tell me more about the OCX. What libraries are you using within it?

I did use the setup wizard to create a setup .exe.  It seemed to
work fine on the client machine.  I noticed that it did not
install and register the .ocx.  I did that manually.  The setup
does not work properly on the machine on which VB is installed
and the one on which I developed the .ocx. I get the following:

%% PLEASE DO NOT MODIFY OR DELETE THIS FILE! %%
 %% This file contains information about the installation of an application. %%
 %% It will be used to automatically remove all application components from your computer if you choose to do so. %%


NOTE: Beginning of the bootstrapper section

CONFIG: Title: "SigCapPrint"

ACTION: TempFile: "C:\WINDOWS\setup1.exe"
(File was not found or was an older version -- new file copied)

ACTION: RegKey: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion", "SharedDLLs"

*** ERROR: Failure writing to the system registry.  The registry may be corrupt, or you may not have the required permissions to write to the registry.
*** ERROR: (User Responded with 'OK')
*** DURING THIS ACTION: SharedFile: "C:\WINDOWS\SYSTEM\VB5StKit.dll"
*** (File currently on disk was already up to date)

Here is the dependancy file:

[Version]
Version=1.0.0.0

[MSVBVM50.DLL <0009>]
Register=$(DLLSelfRegister)
Dest=$(WinSysPathSysFile)
Date=7/19/1997
Time=15:55:40
Version=5.1.43.19
CABFilename=MSVBVM50.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb5
CABINFFile=MSVBVM50.inf
CABRunFile=
Uses1=

[STDOLE2.TLB <0009>]
Register=$(TLBRegister)
Dest=$(WinSysPathSysFile)
Date=5/19/1997
Time=8:08:12
Version=2.20.4118.1
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=OleAut32.dll
Uses2=OlePro32.dll
Uses3=AsycFilt.dll
Uses4=

[OLEAUT32.DLL <0009>]
Register=$(DLLSelfRegister)
Dest=$(WinSysPathSysFile)
Date=5/19/1997
Time=8:08:12
Version=2.20.4118.1
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=

[OLEPRO32.DLL <0009>]
Register=$(DLLSelfRegister)
Dest=$(WinSysPathSysFile)
Date=5/19/1997
Time=8:08:12
Version=5.0.4118.1
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=

[ASYCFILT.DLL <0009>]
Register=
Dest=$(WinSysPathSysFile)
Date=5/19/1997
Time=8:08:10
Version=2.20.4118.1
CABFilename=AsycFilt.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb5
CABINFFile=AsycFilt.inf
CABRunFile=
Uses1=

[CTL3D32.DLL <0009>]
Register=
Dest=$(WinSysPathSysFile)
Date=8/21/1996
Time=0:00:00
Version=2.31.0.0
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=

[COMCAT.DLL <0009>]
Register=$(DLLSelfRegister)
Dest=$(WinSysPathSysFile)
Date=10/31/1996
Time=0:00:00
Version=4.71.1441.1
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=

[COMDLG32.OCX <0009>]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
Date=7/19/1997
Time=16:00:32
Version=5.1.43.19
CABFilename=ComDlg32.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb5
CABINFFile=ComDlg32.inf
CABRunFile=
Uses1=ComCat.dll
Uses2=

[TLBINF32.DLL <0009>]
Register=
Dest=$(WinSysPath)
Date=1/16/1997
Time=2:17:48
Version=1.1.37.15
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=

[SETUPCTL.DLL <0009>]
Register=
Dest=$(WinSysPath)
Date=1/6/1998
Time=13:42:56
Version=1.1.0.6
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=

[INVSIGN.OCX <0009>]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
Date=9/11/1998
Time=10:31:18
Version=1.0.0.0
CABFilename=; If you are going to compress this file into a Cabinet (.cab) file, you should add the name of that file here.
CABDefaultURL=; If you specified a CABFileName, then you can put URL location here, where Internet users can locate your Cabinet file for download.
CABINFFile=; If you specified a CABFileName that processes an INF file, you should put the name of the inf file contained in that Cabinet file, here.  This is ignored if a Run= key is also present
CABRunFile=; If you specified a CABFileName that processes an EXE file, you should put the name of the exe file contained in that Cabinet file, here.  This takes precedence over the InfFile= key
Uses1=MSVBVM50.dll
Uses2=StdOle2.tlb
Uses3=OleAut32.dll
Uses4=OlePro32.dll
Uses5=AsycFilt.dll
Uses6=Ctl3d32.dll
Uses7=ComCat.dll
Uses8=COMDLG32.OCX
Uses9=TLBINF32.DLL
Uses10=SETUPCTL.DLL
Uses11=MsStkPrp.dll
Uses12=

[MSSTKPRP.DLL <0009>]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
Date=7/19/1997
Time=8:26:10
Version=5.1.43.19
CABFilename=MsStkPrp.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb5
CABINFFile=MsStkPrp.inf
CABRunFile=
Uses1=

Any Ideas?

Is your client m/c a windowsNT . If yes logon as admin and try installing
reply back

The development machine that fails on the setup is Windows 95.
The production app is run on Windows NT server.  Both machines
give me a type library error when I try to access the .ocx from
the client app, which happens to be Progress not VB.

Are you logged in with Administrator account or equivalent on the NT Server when you are installing?

Yes the account has full permissions.  

I believe my problem has something to do with versioning.  I set
binary compatibility on and the control stopped giving me the
type library error.  However, when I ran my client app it caused
an irrecoverable error, invalid page fault.  The compile did
produce error pointing to a class and event that no longer exist.

I created a new project, copied the code, but I used the old
names.  The control compiles cleanly, but I am back to the
type library error when I try to access the .ocx in my client
app.  I don't know what all of this means as I am a newbie.

TIA
Jodi

Before compiling your client application create the dependency file for the control to shipped. Let at this point of time version compatibality be project compatible. then compile the client application and try installing your application. Let me know what happens.
 If possible send me the control to siriger@usa.net let me check it out.

please currect my email sirigere@usa.net