B
bart.syryn
Guest
Hi Laura, Thanks for replying. It's adding the sortindicator that breaks the batching. The temp-table definition is: DEFINE TEMP-TABLE tt-post NO-UNDO BEFORE-TABLE tt-post-before FIELD postid AS INTEGER LABEL 'Postid' FORMAT '>>>>>>9' INITIAL '0' FIELD postnummer AS CHARACTER LABEL 'Postnr.' FORMAT 'X(12)' INITIAL '' FIELD plaats AS CHARACTER LABEL 'Plaats' FORMAT 'X(40)' INITIAL '' FIELD provincienr AS INTEGER LABEL 'Provincie' FORMAT '>>>9' INITIAL '0' FIELD searchfield AS CHARACTER LABEL 'Searchfield' FORMAT 'X(256)' INITIAL '' FIELD sysusrcdpost AS CHARACTER LABEL 'Gebruiker' FORMAT 'X(24)' INITIAL '' FIELD sysdatumtijdpost AS DATETIME LABEL 'Datum/tijd' FORMAT '99/99/9999 HH:MM:SS.SSS' FIELD sysactiepost AS CHARACTER LABEL 'Actie' FORMAT 'x(10)' INITIAL '' INDEX plaats plaats postnummer INDEX postid postid postnummer plaats INDEX postnr postnummer plaats. The definition of the bindingsource is build on this temp-table (read the include-file). The handle of the bindingsource is set to the handle of the dataset ( bindSrcpost:HANDLE = DATASET dspost:HANDLE.). The ultrawingrid is attached to that bindingsource. In the ultrawingrid I show three columns (postid, postnummer and plaats). It seems that the ultrawingrid always uses the first index (plaats) to sort the data. If I change my include file so that postid is the first index in the definition, the ultrawingrid uses that index. When I don't use my sortindicator, the batching is just working fine. But when I add my sortindicator, the batching isn't working anymore and I only get my first 20 records (defined for batching). Kind regards Bart
Continue reading...
Continue reading...