[AccessD] Access 2021 LTSC 14332.20416 vs 14332.20345 "command or action 'saverecord' isn't available now. 2046

[Ryan W]

The workstations are identical hardware from a refresh in 2019.  I can't
repro it on my machine (identical hardware) but I'm running Office 365 and
not 2021 LTSC.

Testing a rollback or maybe me.dirty = false in place of DoCmd.RunCommand
acCmdSaveRecord...

Underlying form module hasn't been changed in some time, only Office got
some patches.

On Tue, Nov 15, 2022 at 11:32 AM Jim Dettman via AccessD <
accessd at databaseadvisors.com> wrote:

>
>  Keep in mind that it may not be Access.
>
>  Depending on what was done in the code, a slower/faster machine can
> trigger
> something like this, or just a difference in the way two builds execute.
> Everyone tends to think of Access a monolithic product that is single
> threaded, but it's not.  For example, code running in a form timer can be
> executing in the background while something else is going on.   There are
> other situations as well where the order of operations is not what you
> might
> expect yielding errors like this.
>
>  You don't see it as much as you used to because machines have gotten so
> fast, but it can still happen.   Good way to catch this is to put a stop in
> code.  Let it hit it and just wait a few seconds, then hit F5 to continue.
> If you've got your lines numbered and reported as part of your error
> handler
> (vba.erl), then it's easy to know where to put the stop in.  If not, just
> put one at the start of the routine that does the printing and work from
> there.
>
> Jim.
>
> -----Original Message-----
> From: AccessD On Behalf Of Ryan W
> Sent: Tuesday, November 15, 2022 10:25 AM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: [AccessD] Access 2021 LTSC 14332.20416 vs 14332.20345 "command or
> action 'saverecord' isn't available now. 2046
>
> I have one user who's on 16.0.14332.20416, and another beside him still on
> 16.0.14332.20345.
>
> The user experiencing the error message is on the newer version and has a
> sporadic "The command or action 'SaveRecord' isn't available now. 2046"
> when pressing a button that triggers a bunch of printing to a PDF printer
> (as well as some logic that does run DoCmd.RunCommand acCmdSaveRecord
> before the printing starts.
>
> Has anyone seen this bug/regression themselves? I may end up rolling my
> users back.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>