Connect to Pardox via ADO is SLOW!! 1

[rmcmorris]

I'm using ADO in Excel to connect to PDX tables on an NT network.

Connection String is:
ADOcon.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=G:\DBDIR;Extended Properties=Paradox 7.X"

Query for opening Recordset is:
Query$="SELECT Tab1.Field1, Tab1.Field2 FROM Tab2, Tab1 WHERE Tab1.Field3 = Tab2.Field1 AND ((Tab2.Field2='Something') AND (Tab2.Field3 Is Null))"

Recordset Call is:
RST.Open Query$, ADOcon, adOpenStatic

It takes greater than 60 seconds to return data, regardless if only 1 record is returned or more. Size of Tab1 is about 2000 records. Tab 2 is about 10000 records.

Making a similar ADO call to an Access table takes less than 3 seconds.

I have tried playing with ADO Connection/Recordset settings and with BDE settings with no luck. I have confirmed that ADO is properly accessing the Pdoxuser.net file and generating correct .lck files.

Is this just the way that ADO/Paradox work, or are there some tricks out there?

Thanks,

Regan

 

[rmcmorris]

OK, Found the problem. It seems that if you have Microsoft Jet 4.0 SP3 or earlier, this is a real issue. Upgraded to Jet 4.0 SP6 and the queries are now quite fast. Hope this helps somebody else out with the same problems.

 

[footpad]

rmcmorris,

Interesting! Thanks for the update; every scrap of information helps.

Thanks!

-- Lance

 

[rmcmorris]

Here are a few Microsoft Links for additional reading/download:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;230126

http://support.microsoft.com/default.aspx?scid=kb;EN-US;239114

http://support.microsoft.com/default.aspx?scid=KB;en-us;q263561

Regan

 

[TheVampire]

This came at an opprotune time, as I have been bashing my head against a wall for the last several days, trying to figure out why my VB program kept pausing for a great length of time when I was accessing a paradox 7 table. At record # 3276, and every multiple of that record #, it would pause ( for a very long time ) on the recordset.movenext command.

Questions to the VB forum did not result in any answer.

Upgrading to SP6 fixed the problem!

Thank you. I would issue a star, but for some reson every time I try, it gives me an error.

Robert