I have a customer who runs a custom app based on a Paradox 9 database. Approx 25 users running on a SBS 2008 system. All the PC's are running XP Pro SP3. The database lives on a Windows Storage Server 2003 box. Since we have been replacing PC's that were giving problems, we also seem to have increased the number of corruptions occuring in the database tables. There are two tables that are the regular offenders, being the ones that get thrashed the most. They currently store approx 100,000 records in each table. There has always been an issue of corruption since the system was implemented (apparantly, as this was before we took over their IT) but it has now increased to occuring on a daily basis.The error we get is 52 level 2, BTree errors. Always seem to be pointing at the same record(?!?)
Things tried so far:
1. Change the local setting in BDE Admin - no effect
2. The database was moved to a linux based NAS to try and rule out the opp-locks issue - no effect.
3. Tried to rebuild the tables by creating new tables and importing the data from a CSV export. This appeared to be OK, but when the program was run we got all sorts of index based errors.
I used to be a VB programmer, but have NO experience of Paradox, can anyone offer help or shed some light on what might be causing this? Any pointers will be very much appreciated!
make sure that your virus check programs are excluding your data directories. If you are running virus check on server and PC's make sure that they all exclude the data directories.
Thanks for that, I know the network drives that host the database are excluded, but I'm not sure about the local temporary folder. I will check these today!
Did you try and use the paradox table rebuild utility? This is one of the best methods of rebuilding table and it includes the secondary indexes. I suspect that in recreating the tables you missed an index or didnt include all the fields in an index.
Paradox
Print This
