Re: Failed to load control "HBX"

Lists: pgadmin-support
From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Thomas Sandford'" <thomas(at)paradisegreen(dot)co(dot)uk>, pgadmin-support(at)postgresql(dot)org
Subject: Re: Failed to load control "HBX"
Date: 2001-09-28 07:20:49
Message-ID: AA30E7BCCA5C1D4E88A231900F8325C00B3A@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgadmin-support

> -----Original Message-----
> From: Thomas Sandford [mailto:thomas(at)paradisegreen(dot)co(dot)uk]
> Sent: 27 September 2001 18:55
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] Failed to load control "HBX"
>
>
> Whenever I try to run pgAdminII I get the message
>
> Runtime error '372':
>
> Failed to load control 'HBX' from HighlightBox.ocx. Your
> version of HighlightBox.ocx may be outdated. Make sure you
> are using the version of the control that was provided with
> your application.
>
>
> I get the same results with both 1.1.34 and version 1.1.28.
>
> I am running on Windows 98SE. I used windows installer to
> install first version 1.1.34, and then, when that failed to
> work, version 1.1.28. I de-installed the previous version
> before trying the next.
>
> Any suggestions?

Hi Thomas,

Hmm, that's a new one. Can you please uninstall any copies of pgAdmin that
you have installed, and then confirm that the C:\Program Files\pgAdmin2
folder has been removed.

Next, please check that Highlightbox.ocx is no longer anywhere on your PC
(it normally lives in C:\windows\System). If it is, before removing it, try
unregistering it with (from the Start -> Run box):

regsvr32 /u C:\Path\To\Highlightbox.ocx

Once you are happy that pgAdmin is *completely* removed, then please try
re-installing 1.1.34 (forget about 1.1.28 - the error you have is unlikely
to be caused by a specific version of pgAdmin).

Please let me know how you get on.

Regards, Dave.


From: "Thomas Sandford" <tdgsandf(at)paradisegreen(dot)co(dot)uk>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Failed to load control "HBX"
Date: 2001-09-28 12:21:18
Message-ID: 001001c14818$13d92f20$0300000a@paradise
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgadmin-support

"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> wrote:
> > From: Thomas Sandford [mailto:thomas(at)paradisegreen(dot)co(dot)uk]
> > Sent: 27 September 2001 18:55
> > To: pgadmin-support(at)postgresql(dot)org
> > Subject: [pgadmin-support] Failed to load control "HBX"
> >
> >
> > Whenever I try to run pgAdminII I get the message
> >
> > Runtime error '372':
> >
> > ...
> Hmm, that's a new one. Can you please uninstall any copies of pgAdmin that
> you have installed,

Done.

> and then confirm that the C:\Program Files\pgAdmin2
> folder has been removed.

Done - it had been removed.

> Next, please check that Highlightbox.ocx is no longer anywhere on your PC
> (it normally lives in C:\windows\System). If it is, before removing it,
try
> unregistering it with (from the Start -> Run box):
>
> regsvr32 /u C:\Path\To\Highlightbox.ocx

Done - there was no copy remaining on the system.

> Once you are happy that pgAdmin is *completely* removed, then please try
> re-installing 1.1.34 (forget about 1.1.28 - the error you have is unlikely
> to be caused by a specific version of pgAdmin).
>
> Please let me know how you get on.

Nope - same results.

I've had a poke about the registry, and it looks as though the control is
being registered - at any rate there are entries for

HighlightBox.Properties
HighlightBox.HBX
HighlightBox.TBX

Unregistering and re-registering the ocx using RegSvr32 does not seem to
help. Neither does replacing version 2.00.39 of the OCX from the
installation with version 2.00.41 from the binaries in CVS (unregistering
and re-registering before/after replacement).

Trying to run pgAdmin with the OCX unregistered produces exactly the same
result. Trying to run it if the OCX has been unregistered and _deleted_
causes the install to run and replace the missing file before running
pgadmin (which then fails as "normal").

Any more ideas?
--
Thomas Sandford