Community Forums
Results 1 to 2 of 2

Thread: Self registering OCX did not!

  1. #1
    Join Date
    Oct 2001
    Posts
    44,727

    Self registering OCX did not!



    I included Crescent's Listbox as one of the OCXs to install and marked
    in the SWDEPEND.INI that it was self-registering. When I ran the program
    after the install it said was unable to load the control. What's up?

    Jim

  2. #2
    Join Date
    Oct 2001
    Posts
    44,727

    Re: Self registering OCX did not!



    Jim,

    I had a similar problem with Crystl16.ocx. Here's what my SWDEPEND.INI
    entry needed to look like:

    [CRYSTL16.OCX]
    Register=$(DLLSelfRegister)

    [CRYSTL16 OCX]
    Src=<WINSYS16DIR>
    Uses1=CRYSTL16.OCX
    Uses2=CRPE.DLL
    Uses3=CRXLATE.DLL
    Uses4=uxddisk.dll
    Uses5=uxfdif.dll
    Uses6=uxfrec.dll
    Uses7=uxfsepv.dll
    Uses8=uxftext.dll
    Uses9=pdbdao.dll
    Uses10=pdctdao.dll
    Uses11=pdirdao.dll
    Uses12=pdsodbc.dll
    Uses13=PDBBND.DLL
    Uses14=MFCOLEUI.DLL

    Note that the first entry has a "." between the filename and the
    extension, while the second does not. This is Very Important (and was the
    source of all my problems)! The first entry tells InstallShield to
    register this file, while the second lists all of the files that accompany
    the file. Maybe this kind of entry is required for your OCX as well.

    Good Luck,

    Steve Locke
    HBO & Company


    Jim Poland <jim.poland@csipros.com> wrote in article
    <3288A0C3.7DB0@csipros.com>...
    > I included Crescent's Listbox as one of the OCXs to install and marked
    > in the SWDEPEND.INI that it was self-registering. When I ran the program
    > after the install it said was unable to load the control. What's up?
    >
    > Jim
    >

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •