VB6 and Access 2000

[UncleT]

I have an application written in VB6 with SP5. I am using ADO with Jet 4.0 to store and retreive data from an ACCESS 2000 database. I have the database stored on the server so multiple users can get to it.

The application works fine on my machine but when I installed it on another machine some weird things are happening.

I have a simple select statement that looks like this.
Select * from trainsch where
ucase(keyword) = ucase(g_str_keyword) and
ucase(Category) = ucase(g_str_category)

If this recordset retreives any records a message box will pop up explaining the record already exists.

The problem I am having is that when I execute this SQL statement I get the message box because the record is already out there on the database, but on the other machine I installed the application executes the SQL statement it is like it doesn't retreive a record. I don't get any error messages it just don't find the record.

The only differences, I can think of, between the machines are I have ACCESS 2000 and the other machine has ACCESS 97.

Would this be the cause of this problem and if so how can it be fixed.

Thanks

Tim Morrow
morrow_tim@cityofgastonia.com

 

[TerpFan2001]

I'm not positive but I think Access 97 uses a different OLEDB Provider for ADO connections than Access 2000. OLEDB 3.51 as opposed to OLEDB 4.0.

 

[UncleT]

The acutal database is in Access 2000 which is stored on the server. My question is, is it possible for these things to happen if the application was stored on a machine that has access 97. The application stills gets the data from the Database on the server but the host machine has Access 97 on it? I don't know if it is a DLL problem or what? I tried to use the 3.51 version but it wouldn't connect to the Access 2000 Database. Any help would be appreciated.

 

[MarcLara]

UncleT,
You have an interesting problem here. Do you have the same mdactyp on both machine?

 

[MasterWarlock]

access97 uses the provider for 3.51 and 2000 uses 4.0.
you cant possibly use an access2000 with a computer running the 3.51 version. i suggest you convert your access2000 database to 97, this way both 97 and 2000 can use them. if you have further questions, let me know.

 

[MarcLara]

It is possible to use an OLEDB4.0 on an Access97 database ( I am working on one right now) but I am not sure if you can use OLEDB3.51 on Access2000.