Next Record bizzareness at 200, 400, 600...?

OK, I plead guilty to using an old version of Servoy: “R2 2.0 rc10 build-268 on Linux using Java 1.4.2_03” - but, I’d still like to know if this bug has been found and fixed.

When executing a find which results in a “large” foundset (i.e. >200 records found) a bizzare error occurs at every multiple of 200 errors whilst stepping through the foundset. I.e. after executing the find Servoy has the first 200 records loaded; all is fine till we get to the 200th record. In an interactive form with the 199th record displayed and the total record indicating “200+” executing “Next Record” results in redisplay of the 199th record (and the total changes to “400+”).

In javascript it’s a bit different. A script like this:

controller.find();
// search criteria
controller.search();
var j = databaseManager.getFoundSetCount(foundset);
for(var i = 1; i<=j; i++)
{
  controller.recordIndex=i;
  // process current record
}

processes records 1, 2, … 198, 199, 199, 201, 202, … 398, 399, 399, 401 etc :-(

Looking over the fixes since rc10, I can’t see anything that matches this. Nor can I turn up anything likely in this forum. So, I remain curious as to if this has been “found and fixed”.

Thanks,
Neale.

This issue will be fixed in Servoy 2.04 (and Servoy 2.1 beta3)