A table, as defined in the SQL standard, has no order. It is just a
record bucket.
The design choice of placing the new record at the bottom may have
historical background, or just code simplification urges. Most
environments that let me add new records, do so at the end of the list.
When you insert a new record, there is nothing to derive its sorted
order position from, so the only available location would be at the very
top. If that is what you want to see, you may try to program this. If
your records have a primary key that is invisible to the user, or cannot
be manipulated, you can create a command button that does the insert of
a new record, sort descending on the primary key, and set focus to the
new record. The last step shouldn't need coding because when you sort a
table, the first record will become current, and if you've inserted a
new one, that will likely be the one with the highest key.
Stack wrote:
:)
So what you are basically saying is that Access always inserts a record
at the end of the row regardless of the way it was sorted and that I
have to trick to get what I want? If so, so be it.
--
Bas Cost Budde, Holland
http://www.heuveltop.nl/BasCB/msac_index.html
For human replies, replace the queue with a tea
