There is actualy a space there after Record

Private Sub Form_Current()
   ' RecCountBox = Me.Recordset.RecordCount
    RecCountBox = Me.Recordset.AbsolutePosition + 1 & " of " & Me.Recordset.RecordCordset
End Sub

Private Sub Form_Load()
    DoCmd.GoToRecord , , acNewRec
End Sub

In Form_Current, RecCountBox = the last variable should be Me.Recordset.RecordCount not Me.Recordset.RecordCordset

Aside from that, have you done a Debug Compile? That may be enough to stop Access from compiling the VBA and running.

Yep, Donald found the typo. 'RecordCordset' should be 'RecordCount'. Run Debug > Compile after fixing that, because a compile error elsewhere in the form's module can keep your event procedures from running properly.

Also, make sure the event procedure is named 'Form_Load', not 'From_Load'. Your later post has it correct.

I Debugged and it still won't open to the new record.


Private Sub Form_Current()
   ' RecCountBox = Me.Recordset.RecordCount
    RecCountBox = Me.Recordset.AbsolutePosition + 1 & " of " & Me.Recordset.RecordCount

    
    
End Sub




Private Sub Form_Load()
    DoCmd.GoToRecord , , acNewRec
End Sub

It's okay.
Thank you!

Do you have any other code that runs between/after the Form_Load and Form_Current Events that might be moving the record pointer?

And also, verify in the your form's Event tab in design view that it has [Event Procedure] next to the On Load and On Current Events. Since you changed one or more names, it may not be there. If not, you can either choose it from the drop down on that line or just double-click that line until it says "[Event Procedure]".

It seems from your post that the procedure was originally written as From_Load and later renamed to Form_Load. Access only executes a procedure if the corresponding property on the Event tab displays Event Procedure. Manually editing the procedure name does not establish this connection. Because of this, Debug & Compile passes without errors, but the code never runs. This is precisely the point Donald pointed out. You should check this first.

When Form_Load goes to a new record Form_Current is triggered. On a new uncommitted record Recordset.AbsolutePosition may not return a valid position and can cause an error. RecordCount can also be inaccurate in a dynaset if all records have not been loaded yet. Form Current can be written in a more reliable way like

Private Sub Form_Current()
If Me.NewRecord Then
RecCountBox = "New Record"
Else
RecCountBox = Me.CurrentRecord & " of " & Me.RecordsetClone.RecordCount
End If
End Sub

Form settings might be blocking new records. If Allow Additions = No then acNewRec fails silently. And if the form record source is an uneditable query like some JOIN or Group By queries new records cannot be added.