DrJax
asked on
ADODB and Access 97 Problem
Using VB6. Developed a simple prg for use at my office. Overcame a setup problem (thanks guys), but now have a different problem.
My machine at home has XP Pro and MSOffice 2003. So my dbconnection is to a MSAccess 2003 db. At the office I have Windows ME and Windows 98, both with Office 97. Compiled and loaded, the prg works perfectly at home. I converted the db to Access 97, recompiled and packaged. Took it to the office. It loaded ok and went through its steps, but now it does not load the data to the tables in the Access 97 db. Is there a problem in using ADO with 97? All code remains the same as at home, but Access 97 did notify me that changes were made to the code for the db.
What do I need to do???....jb
My machine at home has XP Pro and MSOffice 2003. So my dbconnection is to a MSAccess 2003 db. At the office I have Windows ME and Windows 98, both with Office 97. Compiled and loaded, the prg works perfectly at home. I converted the db to Access 97, recompiled and packaged. Took it to the office. It loaded ok and went through its steps, but now it does not load the data to the tables in the Access 97 db. Is there a problem in using ADO with 97? All code remains the same as at home, but Access 97 did notify me that changes were made to the code for the db.
What do I need to do???....jb
That is correct if you want to make changes in Microsoft Access itself.
You can access and change data as well as table structures using ADO with Micosoft Access 97 and >=2000.
I'm not sure what u're doing with the data. Do you receive error messages on creating the connection and/or recordset objects? If so, this might be because u're probably refering to an ADO library 2.x where x is higher than the latest ADO drivers installed on the computers at the office. ie: you developed at home, refering ADO 2.8, while the latest version at the office might be 2.5.
U can use ADO 2.5, 2.6, 2.7, 2.8, ... to connect to Access 97 AND Access 2000 databases. No problem at all...
Another thing is the connection string. The database provider may be Jet 3.51 (Access 97 only) or Jet 4.0 (Accesss 97 and Access 2000 or higher).
For your information, Access 2000 is fully INcompatible with Access 97 due to significant changes in the Microsoft Access object library. Access 2002 and access 2003 ARE fully backward compatible with Access 2000.
If you could provide us more information about what u're doing with the databases and what errors you get then I'll probably be able to help you some more.
Cheers,
Luc
You can access and change data as well as table structures using ADO with Micosoft Access 97 and >=2000.
I'm not sure what u're doing with the data. Do you receive error messages on creating the connection and/or recordset objects? If so, this might be because u're probably refering to an ADO library 2.x where x is higher than the latest ADO drivers installed on the computers at the office. ie: you developed at home, refering ADO 2.8, while the latest version at the office might be 2.5.
U can use ADO 2.5, 2.6, 2.7, 2.8, ... to connect to Access 97 AND Access 2000 databases. No problem at all...
Another thing is the connection string. The database provider may be Jet 3.51 (Access 97 only) or Jet 4.0 (Accesss 97 and Access 2000 or higher).
For your information, Access 2000 is fully INcompatible with Access 97 due to significant changes in the Microsoft Access object library. Access 2002 and access 2003 ARE fully backward compatible with Access 2000.
If you could provide us more information about what u're doing with the databases and what errors you get then I'll probably be able to help you some more.
Cheers,
Luc
...if it's the ADO version, you should install the latest MDAC drivers from microsoft. Currently, that version is 2.8:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en
Hi
If your probelm is still not solved plz let me know the connection string you are using.
If your probelm is still not solved plz let me know the connection string you are using.
ASKER
IThema: Downloaded the 2.8 version. Tried to load. Received the following error....."MDAC 2.8 RTM is incompatible with this version of Windows. All of its features are currently part of Windows." I don't understand, since my setup list shows MDAC 2.0????
sandygad: Connection string is ....
Set conData2 = New ADODB.Connection
With conData2
.Provider = "Microsoft.Jet.OLEDB.4.0"
.ConnectionString = "Data Source=C:\Program Files\Progress Notes\patient info2.mdb"
.Open
End With
The prg runs on the new machine with 98 & ME, but does not save the data to the table....so the report prints blank. I'll be happy to send the vbp to anyone who wants to check it out. It's just for use at my office, but we have different operating systems.....jb
sandygad: Connection string is ....
Set conData2 = New ADODB.Connection
With conData2
.Provider = "Microsoft.Jet.OLEDB.4.0"
.ConnectionString = "Data Source=C:\Program Files\Progress Notes\patient info2.mdb"
.Open
End With
The prg runs on the new machine with 98 & ME, but does not save the data to the table....so the report prints blank. I'll be happy to send the vbp to anyone who wants to check it out. It's just for use at my office, but we have different operating systems.....jb
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
U could also send me a sample: LHPDerckx@hotmail.com
Please also state where things go 'wrong' or not as expected...
Of course, I will treat your files confidentially
Sandygad could be right about OLEDB.4.0. It might not work on W98 and ME (What DOES work on Windows ME? :s). I've had a dozen of projects on MSA 2000 and 97, but none of them using W98, ME...
Worst case, you need to write code that uses different provider-versions for different operating systems... I once had code to do that... I'll try to find it.
Maybe you could also try .Provider = "Microsoft.Jet.OLEDB", so you include no version. This is the version independant ProgID. Windows should automatically take its latest version if I'm not mistaken. When searching for "Microsoft.Jet.OLEDB.4.0" and "Microsoft.Jet.OLEDB.3.51"
Cheers
Please also state where things go 'wrong' or not as expected...
Of course, I will treat your files confidentially
Sandygad could be right about OLEDB.4.0. It might not work on W98 and ME (What DOES work on Windows ME? :s). I've had a dozen of projects on MSA 2000 and 97, but none of them using W98, ME...
Worst case, you need to write code that uses different provider-versions for different operating systems... I once had code to do that... I'll try to find it.
Maybe you could also try .Provider = "Microsoft.Jet.OLEDB", so you include no version. This is the version independant ProgID. Windows should automatically take its latest version if I'm not mistaken. When searching for "Microsoft.Jet.OLEDB.4.0" and "Microsoft.Jet.OLEDB.3.51"
Cheers
Thanks
-FA