AddNew method extremely slow for first record added only

[Rich30005]

I have a split database, multi user, Access application (Windows 10 -- Access 64-bit version Office 365).
A particular form where I give users the ability to add a record to the database is unbound. aA user enters all the data in the fields provided on the form, clicks "Add Record". I then run an extensive set of editing checks, then I open a recordset object and use the AddNew method to add the record to a single table that has only one index for an AutoNumber field. Everything works fine, but the first record the user adds can take an annoyingly long time -- like 45 seconds to a minute. Some have reported longer wait times. If the form is kept open and the user enters more records, subsequent added records typically take a second or so at most. To experiment, I executed all the editing checks and added nothing -- those checks take almost no time. I then eliminated all the editing checks and just go directly to add the record -- in that scenario, the first record takes a lot of time and subsequent records happen very fast.
I tried to make the form bound to the underlying table -- I dislike that approach but found pretty much the same pattern. I also tried using VBA to simply construct an INSERT SQL statement (that is, do not user DAO to open a recordset) and got the same annoying result. It seems no matter what I do, that first record takes an annoyingly long time.
If I exit Access altogether so that nothing is cached and open the application again, I can reproduce this result over and over, although on occasion, the first record gets added somewhat faster than described above -- I just cant explain that variation for the first record added.
All idea would be very welcome/
TIA
Rich

[Welshgasman]

It is normal to maintain a connection open to the be all the time?

[CJ_London]

It is probably the overhead of constantly opening a connection

unbound forms will always be slower because on this - you are avoiding using one of the main benefits of access.

You haven’t said but I presume with your split database each user has their own copy of the front end - in which case are all users experiencing the same issue?

have you tried compact repair and decompiling

Also is your table properly indexed?

[moke123]

Have you considered a querydef? No need to open a recordset.

something like

Const Sql_Insert As String = _ 
          "Insert into tblPeople" & _ 
          "(FirstName,MiddleName,LastName,Suffix) " & _ 
          "Values(p0,p1,p2,p3)"


     With CurrentDb.CreateQueryDef("", SQL_Insert)
          .Parameters(0) = Me.FirstName
          .Parameters(1) = Me.MiddleName
          .Parameters(2) = Me.LastName
          .Parameters(3) = Me.Suffix
     .Execute dbFailOnError
     .Close
End With