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

[Ryan W]

Hey Shane,

  I can't tell because the Update History for LTSC only shows WHEN it was
updated, and not what was updated:
https://learn.microsoft.com/en-us/officeupdates/update-history-office-2021

  That page use to contain a changelog (like 365 does here:
https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date
)

   As I said to Jim the codebehind the form hasn't changed in some time,
but Office did get updated about a week ago (give or take depending on when
the computer pulled down the update)

On Tue, Nov 15, 2022 at 11:41 AM Shane Groff via AccessD <
accessd at databaseadvisors.com> wrote:

> Build 14332 is the 2021 Volume License version, and we have made no
> changes in Access for that version, so the problem isn't due to a change in
> Access.  It is possible that changes were made to shared Office code, but
> not likely changes that would impact Access in this way.  You may find that
> rolling back doesn't resolve the issue.
>
> Shane
>
> -----Original Message-----
> From: AccessD <accessd-bounces+shaneg=microsoft.com at databaseadvisors.com>
> On Behalf Of Jim Dettman via AccessD
> Sent: Tuesday, November 15, 2022 9:33 AM
> To: 'Access Developers discussion and problem solving' <
> accessd at databaseadvisors.com>
> Cc: Jim Dettman <jimdettman at verizon.net>
> Subject: [EXTERNAL] Re: [AccessD] Access 2021 LTSC 14332.20416 vs
> 14332.20345 "command or action 'saverecord' isn't available now. 2046
>
>
>  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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatabaseadvisors.com%2Fmailman%2Flistinfo%2Faccessd&data=05%7C01%7Cshaneg%40microsoft.com%7C0c4ea21db047437ac6de08dac72f6913%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C638041303696136770%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=N7zo3PoFy6qECwdJ1o%2FuNI72o8oqSyyyShxTKaQ8JJ0%3D&reserved=0
> Website:
> https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.databaseadvisors.com%2F&data=05%7C01%7Cshaneg%40microsoft.com%7C0c4ea21db047437ac6de08dac72f6913%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C638041303696292990%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lPHYTjQjcN2%2F%2Fpg%2BrgAeBzlmPEJTwmjGRQ8J7oRR7F0%3D&reserved=0
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
>
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatabaseadvisors.com%2Fmailman%2Flistinfo%2Faccessd&data=05%7C01%7Cshaneg%40microsoft.com%7C0c4ea21db047437ac6de08dac72f6913%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C638041303696292990%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Bm%2BHMgBamzNwMKeB1sVVVOE9ax53FkbdQ0YcFM8%2FXPQ%3D&reserved=0
> Website:
> https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.databaseadvisors.com%2F&data=05%7C01%7Cshaneg%40microsoft.com%7C0c4ea21db047437ac6de08dac72f6913%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C638041303696292990%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lPHYTjQjcN2%2F%2Fpg%2BrgAeBzlmPEJTwmjGRQ8J7oRR7F0%3D&reserved=0
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>