Hi guys, thanks for reading my question. I think my biggest problem is that I'm not exactly sure how to even WORD a search for this particular problem, so I've never had any luck on Google or in your search parameters.

When I write a program in Visual Basic 6.0 that just so happens to call a Microsoft Access database file (with msadodc.ocx), it won't read it on another computer that doesn't have VB6 installed. The program loads, and the database is read, but it shows absolutely no information and you can't write to the database at all.

Specifically, on my computer when I look at either the project in progress, or the compiled version of the program, it loads, shows data perfectly, everything. But as soon as Joe Blow on another computer who's testing it out for me runs it, the problem loads, acts like there are no database problems, but then shows absolutely no information from the database. As if it's a clean .mdb file, (which it absolutely is not.)

Note, I've always had problems with the VB Package & Deployment Wizard, so I figured out long ago that if I just include all the needed files in the folder with the program, then there's no installation needed and people can run the compiled program just fine. However, even with all the needed files for anything to do with using msadodc.ocx, the program will run, but show nothing from the database.

What extra files do I need to include in the package to make it run on another computer? I thought at first it was the Microsoft Jet files, but when I attempted to run that it said that a previous service pack had already updated these files. I'm stumped.

Help? Or help me figure out the search parameters to look for it?

Thanks in advance!