Query Result - Bottom row moves to the top, each row moves one down

[Helix51]

Hello,



I'm using Access 2013, getting familiar with the program and hoping to get some advice. I have created a simple database with one table, form and query. The table holds names and basic information about each client. I set the form to view the different records, as well as creating new entries. Finally, I'm trying to set-up the query so that each time I open it, each row moves down one and the bottom moves to the top (is there a term for this?). I don't want it randomized.

1) How can I set it up so that each time I open the query, each row moves down one and the bottom moves to the top?

2) When I add a new entry, how can I do it where it would show up as the top row?

Thank you in advance and if possible, please answer very simple as I'm not familiar with MS Access terminology.

[Micron]

1) you cannot, if I understand the question - with one exception.
2) records are sorted on some field, such as a date. You cannot have all the records in one query sort by date from old to new for example, but have the newest first. That doesn't follow any logical/conventional sort order.

In truth, it should not matter. Queries are for gathering data and presenting in some logical order, but what could be the reason for your quest?

The exception I alluded to would be a UNION query.

[June7]

You can sort records by newest to oldest but the New Record row will always be at the end. Enter new record, commit to table, refresh the form - the new record will be at top.

[isladogs]

You could perhaps fake this effect with two subfoms A and B.
Subfom A jut shows one record - the newest one.
Subform B shows all the others using your preferred sort order.
Place A immediately above B on the main form and give both subforms a transparent border.

However, whilst possible, is it really worth the effort?

[Helix51]

1) you cannot, if I understand the question - with one exception.
2) records are sorted on some field, such as a date. You cannot have all the records in one query sort by date from old to new for example, but have the newest first. That doesn't follow any logical/conventional sort order.

In truth, it should not matter. Queries are for gathering data and presenting in some logical order, but what could be the reason for your quest?

The exception I alluded to would be a UNION query.

I guess the best example would be like food options. Ten restaurants, constantly rotating. This would be the idea.

Is there an alternative to this?

[June7]

Record date restaurant visited. Next restaurant to visit will be record with oldest visit date.

[isladogs]

You have 2 options as already given by micron and myself.
Union query or two subforms.
Both involve a similar idea. Separate the data into two groups with the latest record in one group and the rest in the other.