ODBC interface to legacy Btrieve data files

[Guest_imported]

Hello all,

I have created DDF files for use with Pervasive 2000 SQL to enable acces via ODBC to a legacy Btrieve app. I have used this setup successfully for about a year now. I built the DDF files using DDFedit. Although they work fine my problem is that when I do queries via SQL data manager (and MS Access) it would appear that the indexes are not being used.

This makes using the interface on larger tables (2 million records+ !) out of the question. I end up having to dump the data to an MDB and query it that way.

Do i have to do anything specific to make Pervasive 2000 data manager recognise the indexes?

TIA

 

[Pervasivite]

You should download a file from the Pervasive site called DDFCNV that is in the "Support Toolbox" and read the document with it to determine if DDFEdit uses the old ScalableSQL 3.01 format, that is now over 4 years out of date, for the DDFs. Then once you have a set of DDFs that are in the current format (the difference is relatively minor, but important - they now use some different data types and a bit more of the reserved portion of the record in the DDF file) you should run a consistency check on the DDFs with the Wizard in PCC to determine if the DDFs contain accurate metadata for the file. After that, you should make sure that you have Pervasive.SQL 2000i/SP3 loaded because there have been lots of improvements to the SRDE since the original P2K and SP1. Lastly if all these fail to make it use the indexes properly, contact Pervasive support and enter an incident and get them a test case and they will probably fix it relatively quickly if they find it to be a bug. The incident will cost you about $150 up front, but they will credit you an incident if it is found to be a bug.

Pervasivite