Office LTSC 16.0.14332.20416 "The command or action 'SaveRecord' isn't available now. 2046"

Mindflux

Member
Local time
Yesterday, 18:13
Joined
Jun 25, 2022
Messages
42
Since updating to LTSC 16.0.14332.20416, I've got one user (others haven't seen the upgrade yet) complaining when he hits this button in a form that's got a module behind it that runs DoCmd.RunCommand acCmdSaveRecord then fires a bunch of stuff off to a PDF printer a message box with the title text pops up on him.

Has anyone else seen a regression here? Users still on 160.0.14332.20345 are not experiencing this.
 
usu the form is in a 'state' that cant save due to another process, like currently in an 'edit mode' that has to be completed and return to the form, THEN the save can run.

I get in a form like that, while making changes , i click save, CANT SAVE yet, then simply moving the cursor exits that mode, and allows save.
 
If trying to save the current record in a form you should try to replace the existing Docmd.RunCommand with Me.Dirty=False

Cheers,
 
usu the form is in a 'state' that cant save due to another process, like currently in an 'edit mode' that has to be completed and return to the form, THEN the save can run.

I get in a form like that, while making changes , i click save, CANT SAVE yet, then simply moving the cursor exits that mode, and allows save.

Yeah I get why it tells me that, but in this case the user hasn't edited anything. It seems like some sort of regression from an earlier version of Access(Office) as it's a 'new' problem.
 
If trying to save the current record in a form you should try to replace the existing Docmd.RunCommand with Me.Dirty=False

Cheers,
Yes if rolling back doesn't fix it I am in the process of changing to me.dirty = false instead.
 
but in this case the user hasn't edited anything

Actually immaterial. If the record locks aren't "No Locks" or "Optimistic" then the user has it open for editing and that is a lock. Trying to save via VBA when the form has the same record open can cause the conflict that leads to that message.
 
Actually immaterial. If the record locks aren't "No Locks" or "Optimistic" then the user has it open for editing and that is a lock. Trying to save via VBA when the form has the same record open can cause the conflict that leads to that message.

As I said in the OP the problem didn't manifest itself until a recent Office update. Working on testing that theory here in a bit that a rollback fixes it.

The form/code behind hasn't changed there in some time.
 

Users who are viewing this thread

Back
Top Bottom