- Local time
- Today, 00:01
- Joined
- Feb 28, 2001
- Messages
- 29,385
Actually, that makes sense. GROUP BY (sorting) often puts a strain on any system since it has to create a temporary index internally to assist in the sort operation. I'm not saying Access does this, but other systems I have worked with must have extra disk resources when a SORT is on the line. It would not surprise me to see that Access hit the disk hard for the ORDER BY as well.