Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VB 6 Datagrid Access 97 - can't populate 1

Status
Not open for further replies.

VB6Learner

Programmer
Joined
Feb 2, 2004
Messages
5
Location
US
I have a VB 6 (SP5) problem with Access 97.

Here's the problem:

1) I am trying to use an ADO datagrid control on a VB 6 form. My backend is an Access 97 database.
2) My program works fine on any PC that has VB 6 installed on it
3) My ADO datagrid control will either not populate or give an error and not populate on any destination PC that does not have VB 6 installed on it.

I have researched dependency files, registry settings, and paths, but I can't seem to find the solution.

My latest test:
==========
* Clean install of Win 98 SE
* Installed MDAC
* Installed DCOM 98
* In my dependency file, I have every file listed in my install .lst except for one ADO15.DLL (or something like this); however, this file is on the destination PC and is in the registry.

I will admit that I do not know a whole lot about the registry and dependency files.

Any help would be appreciated!
 

Welcome to TT VB6Learner, to get the most from this site please read FAQ222-2244.

You have to make a setup package and install your program on the destination machine. If you have the learning edition you will not have the PDW (Package Distribution Wizard) that comes with VB and VS (Visual Studio).

Good Luck

 
Thanks for replying. I have used the VB6 Professional package and Deployment Wizard and still it's not working. It seems like the problem is either with a certain file or files not being installed on the destination PC, or something being installed but not registered properly. I could easily be doing something wrong during the Package & Deployment Wizard.
 

You may need to update your MDAC with a later version. Search MS for a listing of available MDAC's.

Good Luck

 
I just found this in Microsoft's knowledgebase. I think my problem is that I am distributing TOO NEW a version of MDAC with my package. It appears that I need the old MDAC 2.0 in my package. Will this hurt PCs that have a newer edition installed???


FROM MICROSOFT:
The "3706: ADO could not find the specified provider" error appears when you try to connect to an Access database through the Jet 3.51 OLE DB provider.
CAUSE
MDAC 2.0 installs version 3.51 of the Jet OLE DB provider. MDAC versions 2.1 through 2.5 install version 4.0 of the Jet OLE DB provider but does not install version 3.51. MDAC 2.1 does not remove or overwrite version 3.51 of the Jet OLE DB provider if it was previously installed.

The Jet OLE DB provider requires the version number of the provider in order to connect to an Access database.

As a result, if your application specifies version 3.51 of the Jet OLE DB provider in the connection string and you install ADO by redistributing MDAC 2.1, you will be unable to connect to your Access database.
 

I don't think so. I have several versions on my dev machines.

Good Luck

 
PROBLEM FIXED: I needed to have MDAC 2.0 installed on the destination PC in order for it to work with Jet 3.51 OLEDB and Access 97.

(For now I had to manually install MDAC 2.0 on the PC because my VB6 Package wants to grab the most current MDAC on my programming PC.)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top