Runtime error 429

20 Mar 2006 3:26 PM

Dave Cullen

One of my VB6 applications has started giving a Runtime Error 429
message. I don't know what changed or why this happened, it's been
running on this machine for 2 years.

According to what I find on the web this could be due to an .ocx file
not being registered. I have instructions for doing that, but how do I
find out what ocx files my application uses?

Any help will be appreciated.

Dave

20 Mar 2006 4:15 PM

Veign

Are you saying that you don't have the code? If its your application don't
you know what components have been used?

--
Chris Hanscom - Microsoft MVP (VB)
Veign's Resource Center
http://www.veign.com/vrc_main.asp
Veign's Blog
http://www.veign.com/blog
--

Show quoteHide quote

"Dave Cullen" <nospam@mail.com> wrote in message
news:441EC9BA.B6495C6D@mail.com...
> One of my VB6 applications has started giving a Runtime Error 429
> message. I don't know what changed or why this happened, it's been
> running on this machine for 2 years.
>
> According to what I find on the web this could be due to an .ocx file
> not being registered. I have instructions for doing that, but how do I
> find out what ocx files my application uses?
>
> Any help will be appreciated.
>
> Dave

20 Mar 2006 5:11 PM

Ken Halter

"Dave Cullen" <nospam@mail.com> wrote in message
news:441EC9BA.B6495C6D@mail.com...
> One of my VB6 applications has started giving a Runtime Error 429
> message. I don't know what changed or why this happened, it's been
> running on this machine for 2 years.
>
> According to what I find on the web this could be due to an .ocx file
> not being registered. I have instructions for doing that, but how do I
> find out what ocx files my application uses?
>
> Any help will be appreciated.
>
> Dave

As Chris mentioned, if it's a project of yours, you should be able to find
out what it needs. There are many ways to get a list. The PDW that ships
with VB is a decent way. It's not that great for installations but it can
surely generate a list for you. You can also just open the VBP file in
notepad and see the list of dependencies.

If it's not your app and the author didn't include error trapping that would
let you know which component is missing, you may be in for a battle. The
easiest fix for that would be to re-install it.

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm

20 Mar 2006 7:43 PM

John Doe

On Mon, 20 Mar 2006 09:11:29 -0800, "Ken Halter"
<Ken_Halter@Use_Sparingly_Hotmail.com> wrote:

>If it's not your app and the author didn't include error trapping that would
>let you know which component is missing, you may be in for a battle. The
>easiest fix for that would be to re-install it.

What about opening the EXE in a text editor in binary mode, and
searching for all occurends of ".ocx"? Maybe another app was installed
recently, and replaced a required OCX with an incompatible-version.

20 Mar 2006 7:52 PM

Ken Halter

"John Doe" <john.***@acme.com> wrote in message
news:nc1u12dij8it35oos54f4ihufavg7i29qk@4ax.com...
> On Mon, 20 Mar 2006 09:11:29 -0800, "Ken Halter"
> <Ken_Halter@Use_Sparingly_Hotmail.com> wrote:
>>If it's not your app and the author didn't include error trapping that
>>would
>>let you know which component is missing, you may be in for a battle. The
>>easiest fix for that would be to re-install it.
>
> What about opening the EXE in a text editor in binary mode, and
> searching for all occurends of ".ocx"? Maybe another app was installed
> recently, and replaced a required OCX with an incompatible-version.

Good luck with that <g> If the app isn't something the author just "threw
together", it shouldn't be too terribly hard to find out which piece is
missing. The 'Hex Editor' approach is a nightmare, to say the least. I'm not
even sure if you'd find a reference to an ocx in there. There might just be
references to CLSIDs.

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm

20 Mar 2006 9:23 PM

John Doe

On Mon, 20 Mar 2006 11:52:26 -0800, "Ken Halter"
<Ken_Halter@Use_Sparingly_Hotmail.com> wrote:

>The 'Hex Editor' approach is a nightmare, to say the least. I'm not
>even sure if you'd find a reference to an ocx in there. There might just be
>references to CLSIDs.

I juste opened a VB5 EXE in TotalCommander, and can see a bunch of
".OCX" strings. Combined with SysInternals' RegMon and FileMon, it
shouldn't be too hard to make a list of required OCX's by trial and
error.

21 Mar 2006 4:23 PM

Dave Cullen

It's not my project, but I'm lucky that I've been able to get the source
from the author.

The PDW generated dependancy file says there are 5 dll's and a .tlb file
that it "uses". Can I tell from these what the .ocx uses are? Or do I
need to look at each control in the project and track down the
associated .ocx?

Thanks

Ken Halter wrote:
Show quoteHide quote

>
> "Dave Cullen" <nospam@mail.com> wrote in message
> news:441EC9BA.B6495C6D@mail.com...
> > One of my VB6 applications has started giving a Runtime Error 429
> > message. I don't know what changed or why this happened, it's been
> > running on this machine for 2 years.
> >
> > According to what I find on the web this could be due to an .ocx file
> > not being registered. I have instructions for doing that, but how do I
> > find out what ocx files my application uses?
> >
> > Any help will be appreciated.
> >
> > Dave
>
> As Chris mentioned, if it's a project of yours, you should be able to find
> out what it needs. There are many ways to get a list. The PDW that ships
> with VB is a decent way. It's not that great for installations but it can
> surely generate a list for you. You can also just open the VBP file in
> notepad and see the list of dependencies.
>
> If it's not your app and the author didn't include error trapping that would
> let you know which component is missing, you may be in for a battle. The
> easiest fix for that would be to re-install it.
>
> --
> Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
> DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm

21 Mar 2006 5:37 PM

Ken Halter

"Dave Cullen" <nospam@mail.com> wrote in message
news:44202890.6A027D2B@mail.com...
> It's not my project, but I'm lucky that I've been able to get the source
> from the author.
>
> The PDW generated dependancy file says there are 5 dll's and a .tlb file
> that it "uses". Can I tell from these what the .ocx uses are? Or do I
> need to look at each control in the project and track down the
> associated .ocx?
>
> Thanks

Yeah.. the dependency file should tell you everything it'll require to get
the app up and running. You can also open the VBP file in Notepad and look
at the list of components. In 99.99% of all cases, reference declarations
start with "Reference=" and control declarations start with "Object=". The
Reference lines show the full path to what ever the reference is pointing
to. The Object lines just show the ocx name (no path)

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm

21 Mar 2006 9:59 PM

Dave Cullen

I've isolated the object that's causing the error, and started a new
thread for that. Thanks for the help so far.

Dave

Ken Halter wrote:
Show quoteHide quote

>
> "Dave Cullen" <nospam@mail.com> wrote in message
> news:44202890.6A027D2B@mail.com...
> > It's not my project, but I'm lucky that I've been able to get the source
> > from the author.
> >
> > The PDW generated dependancy file says there are 5 dll's and a .tlb file
> > that it "uses". Can I tell from these what the .ocx uses are? Or do I
> > need to look at each control in the project and track down the
> > associated .ocx?
> >
> > Thanks
>
> Yeah.. the dependency file should tell you everything it'll require to get
> the app up and running. You can also open the VBP file in Notepad and look
> at the list of components. In 99.99% of all cases, reference declarations
> start with "Reference=" and control declarations start with "Object=". The
> Reference lines show the full path to what ever the reference is pointing
> to. The Object lines just show the ocx name (no path)
>
> --
> Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
> DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm