vksharath
asked on
OLEDB Problem
Hi Experts,
I have a problem with OLEDB Connection. I have a MSACCESS Table with 200 fields when i select a recordset using OLEDB it takes nearly 10 seconds fetch records. Whereas it works good with ODBC. My project is already built on OLEDB so I could not change now. Your help in solving this problem is very much appreciated. ( I use ADO 2.5 libraries with service pack 5)
I have a problem with OLEDB Connection. I have a MSACCESS Table with 200 fields when i select a recordset using OLEDB it takes nearly 10 seconds fetch records. Whereas it works good with ODBC. My project is already built on OLEDB so I could not change now. Your help in solving this problem is very much appreciated. ( I use ADO 2.5 libraries with service pack 5)
The issue I assume is that you are using OLDEB 4.0 with a Microsoft access 97 database. If you change the provider to 3.51 instead of 4.0 you should see a performance increase. The reason being that the OLEDB.4.0 provider is significantly slower at accessing older access databases than the specific provider for access 97. Don't ask me why, ask Microsoft!
how many rows?
do you have a where clause?
do you have a where clause?
ASKER
No it is not with MS ACCESS 97. It is with MS ACCESS 2000.
Hi vksharath,
It appears that you have forgotten this question. I will ask Community Support to close it unless you finalize it within 7 days. I will ask a Community Support Moderator to:
Refund points and save as a 0-pt PAQ.
vksharath, Please DO NOT accept this comment as an answer.
EXPERTS: Post a comment if you are certain that an expert deserves credit. Explain why.
==========
DanRollins -- EE database cleanup volunteer
It appears that you have forgotten this question. I will ask Community Support to close it unless you finalize it within 7 days. I will ask a Community Support Moderator to:
Refund points and save as a 0-pt PAQ.
vksharath, Please DO NOT accept this comment as an answer.
EXPERTS: Post a comment if you are certain that an expert deserves credit. Explain why.
==========
DanRollins -- EE database cleanup volunteer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"You cannot call OLE DB interfaces directly from Visual Basic because OLE DB is a pointer-based interface. A Visual Basic-based client can access an OLE DB data source through ADO."
in the Topic "Accessing Heterogeneous Data with Microsoft SQL Server 7.0"
Roshmon