`
Par2: Pervasive compliant DDFs 2004-12-17 -- Al Henry I'm not familiar with CLA2DDF but I had a similar problem. If your files do not pass the Pervasive consistency tests, then your indexes will be ignored and accessing your files will be done sequentially which can be painfully slow for larger files. Here's a process I used to get my DDF's and files in sync. Use the PCC to create a new table (and new DDF's) and select the 'use advanced settings' checkbox. Specify the location of the existing btrieve file you want the matching DDF to access. Set up the columns and indexes (this may take many iterations and a lot of trial and error but you should be able to make a matching structure). Next save the SQL script generated to create the file. Modify the SQL script if necessary and run the SQL to create the files and indexes. Copy the existing btrieve file into the new SQL file using the Pervasive copy function. Run the consistency test with the new DDF and the new file. You may have to modify the SQL script to handle any errors generated by the consistency test and do the process over (you may need to specify NOT NULL for each field or CASE for strings). Eventually you should be able to get a clean run from the consistency test. Try it out and let me know your results or send me an email if you need more clarification. Printed November 21, 2024, 7:09 am This article has been viewed/printed 35223 times. |