Here is the actual wording on it: "If only one field is specified (one level sort) and it is indexed, the index is used for the order. If the field is not indexed or if there is more than one field, the order is performed sequentially (except in the case of composite indexes). The field may belong to the (selection’s) table being reordered or to a One table related to aTable with an automatic or manual relation. In this case, the sort is always sequential. If the sorted fields are included in a composite index, ORDER BY uses the index for the order.” (http://doc.4d.com/4Dv15/4D/15.3/ORDER-BY.301-3151721.en.html)
-- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <[email protected]> <www.synergyfarmsolutions.com> > Yes, it is smart enough to use a composite index. I think this started in > v11, if I remember right. I think the index only kicks in if there are more > than x number of records in the selection, though. Not sure what x is. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
