Going to need to see your code and properties. Just showing us the Form doesn't help to troubleshoot your problem.

Why not using a macro direct on the main form so that when you want to see that form you simply click the button the form

I have a button on the form that I can click to open the form, but somehow I just don't click on it regularly. And when it opens autmatically on opening the main form i'll see it at least once a day

Try reopening the form in the main form's Activate event.

Private Sub Form_Activate()

    If CurrentProject.AllForms("FollowupF").IsLoaded Then
        DoCmd.OpenForm "FollowupF"
    End If
    
End Sub

@kevin: I don't understand, where do I put this code?

Or just set timerinterval at 100 (1000 = 1 second) and in the on timer event load the form, set the timerinterval at 0 at the end.

Private Sub Form_Timer()
    DoCmd.OpenForm "FollowupF"
    Me.TimerInterval = 0
End Sub

@Marc: Great! That did it, tnx!
Never use the timer event before....

See: Load Faster. Same trick. :)

It helps to know the BIG reason why your second form is behind the first. When Access finishes the Form_Load, the first form still isn't visible. However, the second form will finish all its procedures before the code continues in the 1st form's Form_Load. Modal, popup and acDialog all say to Access that you want the second form to have a priority, although they differ somewhat in how.

If you set breakpoints at the end of procedures, you may find that many procedures may run when opening a form, some even running more than once depending on how your form works. So, this makes it difficult to anticipate where to put the second form's open as it may open twice and cascade problems depending on what that form does. I've caught the Form_Load, Current and Activate procedures running more than once.

Marc's timer trick works because the timer doesn't begin until all the "opening" procedures terminate. You could accomplish the same by finding the last procedure that runs when your particular first form is finished opening, as long as the form is then visible during that procedure. If that particular procedure can run more than once, like the Form_Activate procedure, then you'll need a form module variable (boolean) to allow it to run only once.

There's a small problem with using the timer trick, in that you may legimately use the timer to test for things like logging, user inactivity, network-wide forced shutdowns, etc. Your code can remain in timer (if used as suggested), but you'll still need a form module variable to supress subsequent runs.

Below I'll add a snip of the Status (yellow box) area of my forms. You can see some of the 17 procedures that ran at opening. Look at all the stuff that ran before Form_Current (013)! You can see the Form_Activate running twice (005 & 010). In reality, another 15 "helper" procedures ran, and a simple parameter change can show those procedures too.