> 
hi everyonei have prepared one setup from my machine which is having vb6.0 
and win98 as os, when i dump that setup on other machine having winxp i 
got one error msado26.tlb dependency information not found.
but when i was preparing that setup, i got the same message and got one 
dependency mscom332.ocx but information is out of date.
pls i need help in solving this issuse thanksJames get 2 months FREE* 


"Dwayne" here
I think it would be best to try compiling your project in a NT environment 
eg Win 2000 or XP maybe nt 4.0. It seems to be some compatibilty issue.

Here is a workaround:

When you create your installation package a file called setup.lst is created
and placed in the directory you selected to have your installation package
placed within.

First create a backup of the file.

Open the original file with notepad (remember to uncheck always use this
application to open file) and look for a line that resembles the following
without the quotes:

"File9 = @msado26.tlb,$(WinSysPath),$(DLLSelfRegister),$(Shared),3/26/01
9:13:40 PM,61440,2.61.7326.0"

Change (DLLSelfRegister) to (TLBRegister)

Now save the file back to its original location and try rerunning your setup
exe.

Let us know if this works for you.

Regards,
Tom



----- Original Message -----
From: <dow_2002@y...>
To: "ActiveX_Data_Objects" <activex_data_objects@p...>
Sent: Friday, March 21, 2003 1:04 PM
Subject: [activex_data_objects] Re: getting error while running setup
compiled in vb6.0, msvb26.tlb


> >
> hi everyonei have prepared one setup from my machine which is having vb6.0
> and win98 as os, when i dump that setup on other machine having winxp i
> got one error msado26.tlb dependency information not found.
> but when i was preparing that setup, i got the same message and got one
> dependency mscom332.ocx but information is out of date.
> pls i need help in solving this issuse thanksJames get 2 months FREE*
>
>
> "Dwayne" here
> I think it would be best to try compiling your project in a NT environment
> eg Win 2000 or XP maybe nt 4.0. It seems to be some compatibilty issue.
>
>