Strange databaseManager.getFoundSetCount behavior

Classic Servoy
1

I’m trying to use the databaseManager.getFoundSetCount function (called from an onRecordSelection event) to populate a global to display the total records in a foundset where the number of records are > 200 (testing with a table with ~10000 records). When displaying all records in a table using the loadAllRecords function or with the Show All command or when a table first loads, the resultant value is -1 (no error results). The function appears to return the correct value with any other type of Find, even if the total records in the foundset exceeds 200.

Any idea what I’m doing wrong, or is this a bug? I’m running Version R2 2.0.1-build 274 on Mac OS X.

In case it matters this table has a permanent filter (set at form load) attached using the addFoundSetFilterParam function.

Thanks!

2

first of all. Never call that c onstantly in an on record selection.
Only after a find or loadall.. Anything else will be much to heavy in the end.

I have fixed youre problem with total foundsets. (2.0.2+)

3

jcompagner:
first of all. Never call that c onstantly in an on record selection.
Only after a find or loadall.. Anything else will be much to heavy in the end.

I have fixed youre problem with total foundsets. (2.0.2+)

Thanks for the fix - I really appreciate how responsive you guys have been. Is the fix in beta yet? I’ll check the downloads. Thanks also for the tip regarding onRecordSelect - I’ll move that method once I get scripts written to take over for the default find behaviors.

4

it will not be in a beta but in a fix for the 2.0.x stream.
a new fix (2.0.2) will be released comming monday