When placing command buttons in a form to navigate to the previous or next record, is it best to use the embedded command buttons for the 'go to next' or 'go to previous', when you want the records to appear in descending order?
The reason I ask is, they behave as they should, but to the user they are are in reverse order.
So what I end up doing is setting this up with the 'go to next' as the previous button and the 'go to previous' as the next button? Basically swapping them around.
This works fine but, when I need to add a new record, the user cannot simply click the next record button as it is really not the next record button.
How have you guys dealt with this problem?
I've added another command button to add a new record which works but, I'm curious how the pros do this.
FYI on the form I have the following code which place the records in descending order.
The reason I ask is, they behave as they should, but to the user they are are in reverse order.
So what I end up doing is setting this up with the 'go to next' as the previous button and the 'go to previous' as the next button? Basically swapping them around.
This works fine but, when I need to add a new record, the user cannot simply click the next record button as it is really not the next record button.
How have you guys dealt with this problem?
I've added another command button to add a new record which works but, I'm curious how the pros do this.
FYI on the form I have the following code which place the records in descending order.
Code:
Private Sub Form_AfterUpdate()
'After update,orders desc. OrderByOn = True, setting is applied when object is open.
Me.OrderBy = "[UpdateID] Desc"
Me.OrderByOn = True
Me.Refresh
End Sub
Private Sub Form_Load()
'When form loads,orders desc. OrderByOn = True, setting is applied when object is open.
Me.OrderBy = "[UpdateID] Desc"
Me.OrderByOn = True
End Sub