Re: Adding auto-numbered field screws up Table order
From: Steve Schapel (schapel_at_mvps.org.ns)
Date: 05/30/04
- Next message: DD: "Can't Remotely Open DB w/Linked Tables"
- Previous message: John Vinson: "Re: Adding auto-numbered field screws up Table order"
- In reply to: John Vinson: "Re: Adding auto-numbered field screws up Table order"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 30 May 2004 14:25:48 +1200
John,
If you read my responses carefully, I think you will find that, as is
our wont, we are in perfect agreement on all points. ;-)
-- Steve Schapel, Microsoft Access MVP John Vinson wrote: > Part of the problem (and I'm treading on thin ice here, disagreeing > with Steve!) is that you're assuming that a table HAS an order. It > doesn't. It's an unordered "Bag" of data! Tables will often be > presented for view in sequential order of the table's Primary Key, but > if you use a Query joining this table to some other table, or use the > table as the recordsource of a Report, or a variety of other uses, > you'll see the records in whatever sequence the query optimizer finds > most efficient. > > If you want to sort records in a particular order you must - no > option! - use a Query rather than a table, and the Query must have an > Order By clause sorting the records by specified fields in the table; > or you must set the Order By property of a Form, or the Sorting and > Grouping property of a Report to control the sequence. You *cannot* > count on a table having ANY predictable order. > > John W. Vinson[MVP] > Come for live chats every Tuesday and Thursday > http://go.compuserve.com/msdevapps?loc=us&access=public
- Next message: DD: "Can't Remotely Open DB w/Linked Tables"
- Previous message: John Vinson: "Re: Adding auto-numbered field screws up Table order"
- In reply to: John Vinson: "Re: Adding auto-numbered field screws up Table order"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|