To make sure you are getting all of the necessary drivers for ADO, try downloading the MDAC 2.6 object in Installshield 6.x and including it in your installation. This will probably help with the installation problem. I am currently deploying this on both Win98 and Win2k machines with no problems. As far as the runtime error, I beleive this is due to the method of connecting to the database. When opening the ADO connection object, pass it the driver, database, userid, and password. I generally leave the provider to be selected automatically. Below is a sample for connecting to a SQL Server (MSDE 2000) using ADO.

Public gcnnSQL As New ADODB.Connection
Private lsSQLConnect As String

lsSQLConnect = "Driver={SQL Server};Server={Local};UID=MyUser;Pwd=MyPwd;Database=MyDB"

gcnnSQL.Open lsSQLConnect

You will need to use the correct string for the driver and I beleive the Database parameter is the path and file name of your access database. Replace the other paramters as necessary. This eliminates the need for a DSN configured on the machine that may be changed or deleted. If you prefer a DSN then the same syntax as above would work, but provide the "DSN=MyDSN" parameter in the slSQLConnect string. DAO should be similar. It may be that since the installation creates an error with MSADO20.tlb the DSN being setup in Installshield is not happening and thus the DSN is not found when running the application. If the application still runs I would bet that the connection causing the error is not the primary connection to the database.

Hope this helps.

>I've searched & seen some threads regarding data access problems, MDAC_TYP.EXE, dcom98.exe, etc. I have a product which I am trying to deploy that may get a MSADO20.tlb error while installing with InstallShield (but the product still runs after installation), or has no problems at installation but is getting a
>
>Runtime Error -2147467259 (80004005) [Microsoft] [ODBC File Manager] Data source name not found and no default driver specified.
>
>when the user tries to run.
>
>I don't really want to accept the tlb error, but at least the systems that get it are running OK. My real problem is the 2nd error. It appears from other threads I've seen that MDAC_TYP.EXE needs to be run on the client computer, but I don't know what it does and I couldn't see anything on the Microsoft site that explained what it does. Can someone please explain in a simple list what needs to be run, and where, in order to allow my Access 97 database, which was written on a computer that has W2K and Access 2002, to be able to be used by many people with many different platforms? Where to find these files would also be greatly appreciated--I see MDAC_TYP.EXE in one of the system directories but I don't see any DCOM98.exe file, or even know if I need it. In listing your answer, please don't assume I know anything about it, because I don't--I'm a VFP programmer stuck in a VB loop and I can't get out. We're in the a final beta testing stage before this deploys nationally to 80 district
>managers and I find out it's not working for non-W2K and/or Access 2K computers. Thanks in advance,
>
>Joy
>
>PS--I put this on the Access category last night but haven't gotten any responses so I decided to try the DAO category for more luck :)