Reproducing the Navigation Bar using Command Buttons

[ValerydeMassia]

Hi all! and THANK YOU for your help!

Can someone please assist in making these codes to work? The command buttons are located in the Form footer section. When I run any one of the buttons, I get this:
"Compile error: Method or data member not found."
showing the error to be in the Private Sub Form_Current() section at all the "[...]enabled" lines.
(PS: after this works, I would like to add the "page of page" section of the Navigation Bar.)

Private Sub CmdFirst_Click()On Error Resume Next
DoCmd.GoToRecord , , acFirst
End Sub

Private Sub CmdNext_Click()
On Error Resume Next
DoCmd.GoToRecord , , acNext
End Sub

Private Sub CmdLast_Click()
On Error Resume Next
DoCmd.GoToRecord , , acLast
End Sub

Private Sub CmdNew_Click()
On Error Resume Next
DoCmd.GoToRecord , , acNew
End Sub

Private Sub CmdBack_Click()
On Error Resume Next
DoCmd.GoToRecord , , acPrevious
End Sub


Private Sub Form_Current()
On Error Resume Next
If Me.CurrentRecord = 1 Then
     Me.CmdBack.Enabled = False
     Me.CmdFirst.Enabled = False
Else
       Me.CmdBack.Enabled = True
       Me.CmdFirst.Enabled = True
End If

If Me.CurrentRecord = Me.Recordset.RecordCount Then
        Me.cmdLast.Enabled = False
Else
        Me.cmdLast.Enabled = True
End If

If Me.CurrentRecord >= Me.Recordset.RecordCount Then
        Me.CmdNext.Enabled = False
Else
        Me.CmdNext.Enabled = True
End If


If Me.NewRecord Then
        Me.CmdNew.Enabled = False
Else
        Me.CmdNew.Enabled = True
End If
End Sub

[ranman256]

why would you make more work programming buttons that are built-in to every form?

[pbaldy]

Those are really command buttons? The error implies they are a control that doesn't have that property. Can you attach the db here, or a representative sample?

[moke123]

Here's a navigation bar custom class. Just 3 lines of code in your form.

There are several optional configurations such as cycling records, message boxes, optional buttons, Record n of n label, etc.

Edit: works in the form footer, as well as in subforms (with buttons on either the main form or the subform.)

[Welshgasman]

Crossposted https://www.utteraccess.com/topics/2065307?post=unread

[moke123]

A custom NavBar class is a great example of code portability. Write it once and use it anywhere with just a few lines of code.

Dim clsNB as clsFormNavBar   'in the declarations section

Private Sub Form_Load()


    Set clsNB = New clsFormNavBar
    clsNB.InitCls Me, Me.cmdPrev, Me.cmdNext, Me.cmdFirst, Me.cmdLast, Me.cmdNew, Me.LblCount, Disable


End Sub

[Minty]

why would you make more work programming buttons that are built-in to every form?

Frequently, because you can't disable the free text search function that comes with them.
Try running that on a big dataset with an Azure SQL hosted backend and you'll see why you don't want it there.

Disabling adding a new record without setting the form to allow additions = No would be helpful as well, though isn't quite such a deal breaker.
If those were available options I'd use them a lot more.

[isladogs]

Another reason for 'rolling your own' nav buttons is that the built in controls are fairly small and difficult for some people to use. Also tricky to use when running Access on a touch screen tablet.

[moke123]

Frequently, because you can't disable the free text search function that comes with them.

Never even noticed the text search before. The first thing I usually do is set record selector and Navigation bar to No.
I rarely use them or the custom Nav Bar for that matter. About the only time I turn on the navigation bar is during development to see if the correct number of records are being returned.

[ValerydeMassia]

very sorry for the crossing... won't happen again unless I mention why. Thank you for flagging it.

[ValerydeMassia]

Isladog, that is a very big part of the reason I want this navigation bar. Thank you for expressing it better than I could ever have.

[ValerydeMassia]

Here's a navigation bar custom class. Just 3 lines of code in your form.

There are several optional configurations such as cycling records, message boxes, optional buttons, Record n of n label, etc.

Edit: works in the form footer, as well as in subforms (with buttons on either the main form or the subform.)

Thank You ! Wow! Nice!