Record navigation buttons work backward

[jonesy29847]

I think I hosed my self here, I added an Autonumber field to a table with 277 records in it, I then made the field a key field.



I have record navigation buttons with the following code:

Private Sub Gotonext_Click()
    With Recordset
        If .AbsolutePosition = .RecordCount - 1 Then
        DoCmd.GoToRecord , , acFirst
    Else
        DoCmd.GoToRecord , , acNext
    End If
End With
End Sub

Private Sub GotoPrev_Click()
    With Recordset
        If .AbsolutePosition = 0 Then
        DoCmd.GoToRecord , , acLast
    Else
        DoCmd.GoToRecord , , acPrevious
    End If
End With

End Sub

When I use the Next record button I go to the first, designed in for wraparound, but when I use the Prev button the next record is displayed and Next goes to prev.

[RuralGuy]

Have you tried:
If .AbsolutePosition = 1 Then

[jonesy29847]

I tried to add a key field, and this is the result. It would appear that when I pasted the table the records were pasted backwards. Can someone explain to me what happened.

This code moves to the next record...

Private Sub Gotonext_Click()
    With Recordset
    DoCmd.GoToRecord , , acPrev
End With
End Sub

...and this code moves to the previous.

Private Sub GotoPrev_Click()
    With Recordset
    DoCmd.GoToRecord , , acNext
End With
End Sub

I have hosed myself, and want to know what mistake I made, and how to fix it.

Much thanks.

[RuralGuy]

Why do you have the With Recordset in the code? You are not using it. If you were then your code would look like:

With Me.Recordset
   .MoveNext
End With

[jonesy29847]

No joy.

I really think I have hosed the table somehow when I tried to add an Autonumber key field to the table.

Thanks

[RuralGuy]

Adding an AutoNumber field to a table should not be a problem. Have you already done a Compact and Repair? Any chance you can post your db?

[jonesy29847]

I tried compact and repair, no joy, file attached

[RuralGuy]

I made some changes but it seemed to be working as expected from the jump.

[jonesy29847]

Yes I see the changes, but the next button still moves to the previous record, and the previous button moves to the next record.

When I originally coded the buttons next called DoCmd.GotoRecord,,acNext and vise versa. Then I got the bright idea of adding an Autonumber Key field, after that I was hosed.

[jonesy29847]

Correction, they work correctly, but the underlying code is backward.

[RuralGuy]

Are we talking about the MainForm?

[jonesy29847]

Yes Main.

[RuralGuy]

What underlying code do you feel is backwards?

Private Sub Gotonext_Click()
   With Me.Recordset
      If .AbsolutePosition < .RecordCount - 1 Then
         .MoveNext
      End If
   End With
End Sub
Private Sub GotoPrev_Click()
   With Me.Recordset
      If .AbsolutePosition <> 0 Then
         .MovePrevious
      End If
   End With
End Sub

[jonesy29847]

Perhaps I was a little convoluted in my post. I should have stated

When I use the Next record button I go the the Previous, and when I use the Previous record button I got to the Next

There have been a few iterations with the code, but always the same result, the code that should navigate to the next record navigates to the previous, and vice versa. I initially designed to code to wraparound, to avoid the error message that comes up when you are at either end of the recordset and try to navigate beyond it.

When I first switched record navigation to VB all was well, then I got the bright idea to add the autonumber field and make it the key.

I exported the records to excel, blew the table data away, added the autonumber field and populated it, in excel. When I imported the spreadsheet I was hosed.

Adding to all this confusion the Autonumber field looks correct, the lowest number is assigned to the first record, and the highest to the last.

Whew!

[RuralGuy]

You do know that you have an OrderBy Clause property of the form that sorts descending, right?