Indexing problems in V4RB, again

[Steve Albin]

I have an app that was working fine using V4RB 2.4.3.  I just made some minor changes and rebuilt with V4RB 2.5.9.  I open a database that was opened with the 2.4.3 version and make as many updates as I like to a particular table.  But when I close the datebase and reopen it, the first update to that table fails because of a duplicate unique key.  I do a diagnose and that table reports a mismatch on number of records and number of index records.  I can rebuild the index, and then make updates again.  But as soon as I close and reopen the database, the updates fail with the same problem.  

If I create a new database with the 2.5.9 version, this problem does not occur.  Of course, a new database is not an option as I need to use my current data.

I tried cloning the 2.4.3 database before opening with the 2.5.9 version of the program, but that did not help.

Any ideas on what could be corrupting my index on close and reopen of the database?  

Steve





-- 
Steve Albin - Montclair, NJ
http://www.jazzdiscography.com/
http://www.steve-albin.com/