------=_NextPart_001_0000_01C20625.88475CD0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hello, maybe this can help to the process of installation (The Resolution
 4 work very easy):

BUG: Error "Unable to Register MSADO15.TLB" If You Use a PDW Package to I
nstall a VB Application (Q299645)


The information in this article applies to:


Microsoft Visual Basic Enterprise Edition for Windows, version 6.0 
Microsoft Visual Basic Professional Edition for Windows, version 6.0 





SYMPTOMS
When you use a package that you created with the Package and Deployment W
izard (PDW) to install a Visual Basic application, you may receive the fo
llowing error message (or similar) during the installation: 
Unable to register MSADO15.TLB 
This error message may reference any of the following files: 
MSADO15.TLB 
MSADO20.TLB 
MSADO21.TLB 
MSADO25.TLB 


CAUSE
The Package and Deployment Wizard adds the type library (.tlb) file to th
e package because the type library is referenced in your project. The PDW
 also erroneously assigns the $(DLLSelfRegister) registration macro to th
e type library in the Setup.lst file that is created for your installatio
n package. 

Most commonly, this problem occurs when your Visual Basic project contain
s a reference to a version of ActiveX Data Objects (ADO) that is earlier 
than the latest installed version. The reference for the latest installed
 version of ADO points to MSADO15.DLL. Earlier version references point t
o the above-mentioned ADO type library files. 


RESOLUTION
This file does not need to be explicitly included in your package. If you
 have a reference to an ADO type library in your project, you are utilizi
ng ADO in your application and must distribute Microsoft Data Access Comp
onents (MDAC_TYP.EXE). The only exception is if you can guarantee that th
e correct version of MDAC will already be installed on your target comput
ers. Because the MDAC installer includes the type library, there is no re
ason to include it specifically. 

There are several ways to resolve this problem. Which method you use depe
nds on your circumstances and whether it is convenient for you to repacka
ge the application. In Resolutions 1 and 2, you do not have to repackage 
the application. Resolutions 3, 4, and 5 require repackaging. Resolutions
 4 and 5 are the only long-term fixes and are recommended. 
Resolution 1 
Locate the Setup.lst file for your package. 


In any text editor, open Setup.lst. 


In Setup.lst, locate the line that references the ADO type library that i
s referenced in the error. If you are using Notepad, you can search for t
he file name. 


Change $(DLLSelfRegister) to $(TLBRegister). 


Save the file, and try the installation again. 


Resolution 2 
Locate the Setup.lst file for your package. 


In any text editor, open Setup.lst. 


In Setup.lst, locate the line that references the ADO type library that i
s referenced in the error. If you are using Notepad, you can search for t
he file name. 


Delete this line from Setup.lst. 


Make sure that the File##=3D statements are sequential, and, if necessary
, renumber the lines after the line that you deleted. 


Save the file, and try the installation again. 


Resolution 3 
Start the Package and Deployment Wizard, and open the Package script if i
t was saved. 


Complete the steps in the wizard until you reach the Package and Deployme
nt Wizard - Included Files page. 


Clear the check box next to the ADO type library that is referenced in th
e error message. 


Complete the steps to repackage the application, and try the installation
 again. 


Resolution 4 
Locate the VB6DEP.ini file. By default, this file is located in the C:\Pr
ogram Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\ folder. 


In any text editor, open VB6DEP.ini. 


Locate the [Do Not Redistribute] section. 


Add the following lines to the [Do Not Redistribute] section: 


MSADO15.TLB=3D
MSADO20.TLB=3D
MSADO21.TLB=3D
MSADO25.TLB=3D
Save the file, and close the text editor. 


Repackage your application, and try the installation again. 


NOTE : This method prevents the problem from reoccurring. 
Resolution 5 
Open your project in Visual Basic. 


From the Project menu, click References . Note the version of Microsoft A
ctiveX Data Objects Library that is selected, and select the check box fo
r the ADO reference. If the reference points to a .tlb file, clear the ch
eck box. Scroll the list to find the other versions of ADO, select the la
test version that points to MSADO15.DLL, and click OK . 


Test the project to confirm that the ADO features still work properly. 


Save the project, and then build the EXE. 


Repackage your application, and try the installation again. 




STATUS
Microsoft has confirmed this to be a problem in the Package and Deploymen
t Wizard for Visual Basic 6.0. 


MORE INFORMATION
The error is raised because the PDW attempts to use $(DLLSelfRegister) fo
r type libraries rather than $(TLBRegister). However, if you receive this
 error during installation, it does not necessarily mean that the install
ation will fail. It also does not mean that the application will not run 
after installation. This error does indicate that you may have a differen
t version of the ADO type library referenced in your project than you are
 distributing with your application. This can potentially cause other pro
blems, so Microsoft recommends that you verify the version information. S
ee the "References" section for additional information. 




----- Original Message -----
From: ashay@w...
Sent: Tuesday, May 28, 2002 7:48 AM
To: professional vb
Subject: [pro_vb] RE: Error installing new vb app in client computer, ple
a se help urgen t!

hi,
During installation if u get an error of msado15.tlb,just ignore the erro
r
and continue......but before installing ur app make sure that u download
and run the approproiate MDAC from microsoft site on the clinet
machine.........This will take care of the ado errors....

http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;Q248404

regds,
ashay
>
Hi

msvbvm60.dll is the VB run time dll, you need this dll to registered in
the
computere where you want to run the application, if that PC does not have
Visual studio intalled.

The reason You are getting message "cannot registry msado15.dll", may be
due
to version conflicts.So check the version In your Boss's PC and the versi
on
you are installing, If the version you are installing is newer than alrea
dy
existing, unregistered that and register the newer version ( shd be ANSI
version on Win 98).


V I s h a l  M a h a j a n

-----Original Message-----
From: Zulfazli [mailto:Zulfazli@l...]
Sent: Tuesday, May 28, 2002 8:46 AM
To: professional vb
Subject: [pro_vb] Error installing new vb app in client computer, please
help urgen t!


Hi VBers,

Please help me, urgent!

I have installed my vb on myboss notebook. o/s win98.
When install it raised error, cannot registry msado15.dll. So i ignored t
he
process, and then i continued the installation process.
When i ran the app, it can opened one window (mdi child), but when i open
ed
another window, it crashed, with message cannot load msvbvm60.dll).
What happen to this app ?
And then i try to install to new another pc with o/s win98 and msoffice
software in it.
I install my app, it just raised error when it attempt to registry the
msado21.tlb. I ignore this message, and continue the installation. When i
run the app, it run succecfully. In my deployment script for this app (I
use
Package & Deployement Wizard from VB 6.0), i do not include msado15.dll, 
i
just include the msado21.tlb.
So i repackage again this app with msado15.dll include in the script.
When i install the app to that pc, in installation process it raise error
enabled to registry the both files. I ignore this message, and setup
continue to finish.
But when i run, it raise error "Cannot Create activex object", i suspect
this error raise when the app attempt to connect to database via ado.
So, is this error raise by msado15.dll ?
In my vb pc, i've installed ado ver. 2.0 and ado v. 2.7. When i install a
do
v.2.7 it didnt asked me whether i wanted to installed with ado v.2.0 and
ado
v.2.7 stay separetly in my system.

Can any one help me to point what wrong in my case

Thank for your kind help

Zulfazli

to unsubscribe send a blank email to G
et more from the Web.  FREE MSN Explorer download : http://explorer.msn.c
om