I am experiencing loads of issues with indexes breaking on heavily used tables. Is there a known bug that requires indexes to be rebuilt almost on a daily basis?
The whole thing runs on a desktop PC with WinXP.
I'bve just found out that it's 2 service packs out of date so am updating that first.
The user either runs a VB app to populate the database, or goes into Paradox itself and uses forms & reports.
Normally they would use each method exclusively, but recently they may be opening both at the same time which makes me think of write conflicts.
VB? Well, I'd certainly go to that code and ensure things are being done properly. And that a correct ODBC driver is being used; some versions from M$ don't support proper editing, and some don't support editing beyond Table Level 5.
I think I've found what part of the problem is now.
The production files are moved to a reporting server and in that process one of the .val files wasn't getting updated. I totally refreshed the report server copy of the files and am not getting the error so much now.
I've also stopped the vb app and Paradox db being used at the same time.
Re the ODBC driver, we use Paradox's as Microsofts doesn't support any sort of sharing.
As luck would have it, I did get the error again after I wrote that email.
Then I found some further email therads that said the .val file related to the bad tables can sometimes get confused.
They can be deleted and will get recreated by the database automatcally. Since I deleted those .val files I haven't had any more issues.......so far.
(1) Make sure that all indexes are marked "maintained." If not they immediately are considered "out of date."
(2) Make sure that all tables related to this one have the same "table language." If, for example, table-X is French and table-Y is US_ASCII, you'll always have problems.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.