Custom Navigation buttons stop working when form is edited

[PlayerPianoMan]

Ok I have news. I turned the Navigation button property to off. Opened the form, all the nav buttons are disabled BUT if you click the NEW button and that will activate the buttons and they will work normally. If you exit and reopen the form then you have to click the New button again. Does this help?

[Welshgasman]

Ok I have news. I turned the Navigation button property to off. Opened the form, all the nav buttons are disabled BUT if you click the NEW button and that will activate the buttons and they will work normally. If you exit and reopen the form then you have to click the New button again. Does this help?

I am not sure what you are doing?
Moke's class has nothing to do with the Access navigation buttons?
I just downloded his DB and set them to No, and his buttons work fine?

[moke123]

So there are 3 options with my code. Cycle the recordset, disable the buttons, and a message box.

Your issue only occurs with the disable option. I tried the other 2 options and they seem to work fine.

baffling.

[davegri]

LighthouseCollection-PPM-davegri-v01.zip

See if this works for you.

[PlayerPianoMan]

I have more information. I opened and brand new database, put in a table and form and tried the navigation buttons. Same issue. However I accidentally clicked the new button when the form came up and all the navigation buttons now worked and they worked fine until I exited and then reopened for form. Once again I clicked the New button and everything was ok. I have attached a screen shot of the Current Database settings in Access Options menu.

[moke123]

@Dave

Any insight as to why with my class the buttons are being disabled when the nav button property is changed?
It shouldn't happen as far as I know. I find it a little disturbing.

[PlayerPianoMan]

I also wonder if there is a form setting that could be causing this? I am at a loss.

[PlayerPianoMan]

That works! What did you do?

[davegri]

That works! What did you do?

I adapted your form_current code to the code that I always use for custom navigation.

[moke123]

I think I fiqured it out but still don't understand why.

The form when opened was only loading one record. Therefore it was at BOF and EOF disabling the buttons.

I added a move last/first to the initiating code and that solved the problem

Public Sub InitCls(frm As Form, bPrev As CommandButton, bNext As CommandButton, Optional bFirst As CommandButton = Nothing, Optional bLast As CommandButton = Nothing, Optional bNew As CommandButton = Nothing, Optional lCounter As Label = Nothing, Optional Bof_Eof_Action As eRecordAction = 1)
    Set m_objfrm = frm
    Set m_objcPrevious = bPrev: m_objcPrevious.OnClick = fEvents
    Set m_objcNext = bNext: m_objcNext.OnClick = fEvents


    m_objfrm.OnCurrent = fEvents


    If Not bFirst Is Nothing Then Set m_objcFirst = bFirst: m_objcFirst.OnClick = fEvents
    If Not bLast Is Nothing Then Set m_objcLast = bLast: m_objcLast.OnClick = fEvents
    If Not bNew Is Nothing Then Set m_objcNewRec = bNew: m_objcNewRec.OnClick = fEvents
    If Not lCounter Is Nothing Then Set m_objLblCount = lCounter


    TheAction = Bof_Eof_Action
    
    frm.Recordset.MoveLast
    frm.Recordset.MoveFirst
    
End Sub

[Welshgasman]

Surely if it is loading only one record, it cannot be at BOF or EOF?

[moke123]

Surely if it is loading only one record, it cannot be at BOF or EOF?

True, but you know what I mean. There was no next record or previous record so all the buttons would disable.
Technically I should have said the absolute position of the recordset remained at 0. the absolute position is the criteria which makes the code function.

I put a debug.print me.recordset.recordcount in the onload event. with navigation buttons turned off it was 1, and with it on it was 21.
Not sure why.

[Welshgasman]

Ah, I see, sorry, misunderstood.