Are there dependencies for MSADO20.tlb? {Same as VB5&6} 1

[sugar8ritches]

My application uses an <b>Adodc</b> and <b>Datagrid</b>, and operates normally on the developing PC. When I use the <b>MS Setup/Packaging Wizard</b>, it prompts that there is no dependency info found for <font color=red>MSado20.tlb</font>, and I have not been able to find that there is, so I ignore the message.<br>However when I install the app on a &quot;clean&quot; PC, the first use of the <b>Adodc</b> results in &quot;<b><i>3706: ADO could not find the specified provider</i></b>&quot; which seems to point that there is a conflict with the <b>Jet 4.0</b> engine specified in the connection string and the version of the <b>MDAC</b> (2.0?) on the test PC.<br>My Question is: Are there files that need to go with <font color=red>MSado20.tlb</font> or does that file need to be included at all? I am assuming that this is causing my error. Would installing latest version of <b>MDAC</b> on Developing PC help? Where can a person find all the dependency information on MS products when there are no .dep files for them (it took me 2 days to find out that MShtml.tlb does not need dependant files, I think?) <br><br><br>-Blessed are those with the knowledge

 

[Vince]

I would suggest that you install MDAC 2.1 on both the client andthe development platforms as this rectifies most of the problems that we have all had to suffer with MDAC 2.0 <br><br>The reason that you cannot find .dep information for MDAC2.0 is that it uses the MDAC1.5 dependancy information not it's own, another Microsoft quick fix <br><br>this should solve your problem. If it doesn't then I would suggest that you check your connectionstring. A good way to test it is to try it with a DSN instead of the full connection string.<br><br>cn.connectionString = &quot;DSNName&quot;<br><br>The only other thing that I would suggest is that the ADODC control is not the most reliable control so possibly set up your connection in code, at least that way you will have control over it. If you need an example mail me and I'll be happy to help <br><br><A HREF="mailto:Vincent.Dooher@Unipro.demon.co.uk">Vincent.Dooher@Unipro.demon.co.uk</A><br><br>Hope this is usefull<br>

 

[sugar8ritches]

Thanks for the info Vincent,<br><br>I think that should solve those problems. I finally found <A HREF="

http://support.microsoft.com/support/kb/articles/Q217/7/54.ASP"

TARGET="_new">

http://support.microsoft.com/support/kb/articles/Q217/7/54.ASP</A>

which seemed to make sense since VB6 was showing me I was using 2.1 components but I found a MDAC_typ.exe 2.0 file in the wizard folder. This is just one of the many times I will be jammed by MS, I'm sure.<br><br>Thx again - <br>SB

 

[varthi]

I tried installing MDAC2.1 and I still have the same error.
Is it ok if I ignore the message during packaging and deploying as well as installing it from the setup file ? Also when I try and run my setup program on another machine. It says setup will need to restart my machine and install new files but it ends up restarting my machine and doing nothing. Please help me. Im in a crisis.
Thank you.

 

[ronze]

i had a similar problem with a provider i am using. I would suggest you regester the provider, if you have done this then use the following code as a guide:

'creates the connection string to be used
ConnStr = &quot;Provider=MSDASQL.1;Persist Security Info=False;&quot; & _
&quot;DATA SOURCE=daily_vb&quot;
Set Cn400 = New ADODB.Connection
Cn400.Open ConnStr
Rs400.CursorLocation = adUseClient

strSQL = &quot;select * from [&quot; & ofile & &quot;]&quot;

i used the ole db simple provider for odbc instead of the jet. it looks like you are using the jet provider. which means the provider goes something like this micorsoft.jet.4.0. I also used a datalink to set up my DSN

to regester you use the run option in your start up menu and the following line

regsvr32 &quot;C:\...your directory...\yourdllfile.dll&quot;

good luck

Christina

 

[VBmim]

Note for msado21.tlb

For some reason, the VB installer doesn't recognizes this file as a .tlb but as a .dll and searches for a dll dependency. When your package is created you must edit the .lst file and change the row where msado21.tlb is referenced

File36=@msado21.tlb,$(WinSysPath),$(DLLSelfRegister),$(Shared),4/12/01 2:52:16

becomes

File36=@msado21.tlb,$(WinSysPath),$(TLBRegister),$(Shared),4/12/01 2:52:16

 

[stevearas]

I saw so much info on this error, going back and forth. I really don't know what using the TLBRegister does, but it works. Thanks.

I'll have to do some research on TLBRegister

 

[Guest_imported]

Where do I make the changes?

&quot;File36=@msado21.tlb,$(WinSysPath),$(DLLSelfRegister),$(Shared),4/12/01 2:52:16

becomes

File36=@msado21.tlb,$(WinSysPath),$(TLBRegister),$(Shared),4/12/01 2:52:16 &quot;

In the wizard I only see a choice of adding a fuile and not making changes, Please help me.

 

[Guest_imported]

there should be a file created with a Setup.lst file in your distribution folder. In there you will find this detatiled file distribution.

 

[Guest_imported]

I have created an installer for VB.
My application is using the DLL created by myself.
The problem is that my application is running fine on the m/c where VB is installed.
But it is giving problem on the m/c's where VB is not installed(not creating the object of DLL).
I have registered MSVBVM60.dll & MSAdo20.tlb still i am not getting why is it so.
Please solve my problem.

 

[Guest_imported]

tushar balar (Programmer) aug 22, 2002
Note for msado21.tlb

For some reason, the VB installer doesn't recognizes this file as a .tlb but as a .dll and searches for a dll dependency. When your package is created you must edit the .lst file and change the row where msado21.tlb is referenced

File36=@msado21.tlb,$(WinSysPath),$(DLLSelfRegister),$(Shared),4/08/02 2:52:16

becomes

File36=@msado21.tlb,$(WinSysPath),$(TLBRegister),$(Shared),4/08/02 2:52:16

 

tushar balar (Programmer) aug 22, 2002
Note for msado21.tlb

For some reason, the VB installer doesn't recognizes this file as a .tlb but as a .dll and searches for a dll dependency. When your package is created you must edit the .lst file and change the row where msado21.tlb is referenced

File36=@msado21.tlb,$(WinSysPath),$(DLLSelfRegister),$(Shared),4/08/02 2:52:16

becomes

File36=@msado21.tlb,$(WinSysPath),$(TLBRegister),$(Shared),4/08/02 2:52:16

 

tushar balar (Programmer) aug 22, 2002
Note for msado21.tlb

For some reason, the VB installer doesn't recognizes this file as a .tlb but as a .dll and searches for a dll dependency. When your package is created you must edit the .lst file and change the row where msado21.tlb is referenced

File36=@msado21.tlb,$(WinSysPath),$(DLLSelfRegister),$(Shared),4/08/02 2:52:16

becomes

File36=@msado21.tlb,$(WinSysPath),$(TLBRegister),$(Shared),4/08/02 2:52:16

 

[vbnownzen]

hi guys..

the problem with referencing a type library (TLB) instead a dll is no sweat and can be solved in a # of ways.

ofcourse changing the erroneous refernce to a a tlb in the setup.lst file instead of a dll is the simplest,ther are other options too..

make sure ur application references the latest version of mdac then the one installed on ur sytem..thast the root problem . u cud deslect any refernce to old mdac components fromthe references list in ur project..make sure u derefence only to a tlb...

chill..