Hi Gregory, I'll let Pierre address most of your questions, but I'll share my own DB performance with you and other users: My DB is much bigger : 292 Mb, compacted, 48 173 items. It has tons of VB functions stacked on top of that (but that shouldn't have any effect on refreshing), and... it never ever takes that long to refresh a grid (F5). On my laptop (not that new : 2.2 GHz, Intel core 2 duo T7500), let's experiment : Reference grid : - Filter: reference and item like "*I*" - Source: Reference OR zzReference - Sort rule: itemcreated desc Results : 2701 visible items, 9s. It's not a speed demon, but it's more than 13x faster than yours... :) Task grid (a completely different beast with huuuuge filter and pretty complex sorting rule) : - filter : ((task) and (((urgency >= 90 or (due-now<=0 and urgency >= 110)) or (due is null)) and (followupdate-now<=0 or followupdate is null)) AND (check is null)) and ((ABCD_priority not like "D" and ABCD_priority not like "Z") or ABCD_priority is null) and EnAttente is null and notTLI is null | (Task Or Étape Or Projet or Recurrence) and check is null - Source : Task or zztask - sorting rule : OK, Focus, recurrence, taskStartDurLock, ABCD_priority, urgency desc, priority Results : 82 displayed items, 10.5s... when IQ isn't busy doing something else. Between 13s and 15s while IQ is updating all fields with autoupdate equations (happens around midnight). The only thing I can see is that you might have incredibly complex sorting rules or, maybe, grids with several 1000s of *displayed* items?? Complex sorting rules are deadly, whatever the program is. showing 1000s of items all at once can also be taxing. Personally, I couldn't stand 125 seconds !! There'S definitely something wrong there.