Does your app need a DSN to an MDB? If so, the second error hints that the Setup is not creating the needed DSN on the client's computer. Check for the required DSN under Control Panel-ODBC Data Sources. If indeed this is the problem you could try to create it manually and see if the program runs OK.

And unless you are making calls to a COM component on another PC you probably don't need DCOM98.exe. It would be needed in some older computers with Win9x that didn't have DCOM support.

If a DSN is your problem, then you might want to check what version of MDAC the problem machines are running and compare it to the version of the ones with no issues. The action there is to install the version of MDAC that works.

If you don't need any of this (if you are not using an ODBC driver to your MDB), you probably need to distribute the right version of the Jet runtime. I don't know if Access 2002 would let you distribute an older version of Jet, (or even if it installs it) but you might want to check the project references for the Access97 version of Jet (I think is 3.51).

HTH

>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 :)