[AccessD] Uninstalling Office Update

[Jim Dettman]

 The other way to handle this is to not be on the "bleeding edge" as they say.

 Office is broken up into channels, which determines when you get updates.  The most stable is the semi-annual one (here's a list of the others: https://learn.microsoft.com/en-us/deployoffice/overview-update-channels).   You don't get updates as often (only 2x a year), but you only get updates after a whole lot of other people have tried them out.  By the time they get to you, most of the bugs are well worked out, or workarounds known, which you can plan for.   You can look in Access on the file menu, account, about, and it will tell you which channel you are on.


 The command to switch channels is:

   CD C:\program files\common files\microsoft shared\clicktorun
   OfficeC2RClient.exe /changesetting Channel="SemiAnnual"

   And you do that in an Administrator command window.

   As an aside, it seems something was done with ODBC in the Dec 6th build.   Not sure if it was something the Windows team did or what, but there have been sporadic reports of problems with ODBC.   I have one client where an ETL process that typically ran in 30 minutes (and always finished under an hour), jumped to 7-10 hours.    There's also an issue with the older SQL driver and Windows 11, which many are still using.

   I would suggest changing to the semi-annual channel and see of the problem goes away.   If it does, I'd also suggest staying there for anything that is a production system.

Jim.

-----Original Message-----
From: AccessD On Behalf Of David Emerson
Sent: Thursday, January 12, 2023 10:13 PM
To: 'Access Developers discussion and problem solving' <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Uninstalling Office Update

Thanks Borge,

The tables have not been changed for months and the problem occurs regardless of the table being linked.

I am surprised that there is not an easier way of rolling back an update.

-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On Behalf Of Borge Hansen
Sent: Friday, 13 January 2023 3:55 pm
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Uninstalling Office Update

David,
For what’s it worth, I also link to a SQL db backend without using a DSN. I have a local table - a master of all the names of the tables in the SQL db I need linked. I assume you have the same. I would check that the issue is not with the local master table with the names of sql tables that need linking. Even try to rename the dbo.tblGroup just for the relinking to see if the issue is with the name.
Just my immediate thoughts,
/borge

Ps: apps that I am using removes all linked tables upon closing down of the app. On starting the app - after user has authenticated themselves the app does a full relinking of all tables according to the master list while I’ve got a spinning wheel or similar progress indicator running.




On Fri, 13 Jan 2023 at 07:41, David Emerson <newsgrps at dalyn.co.nz> wrote:

> Hi Listers,
>
> The latest version of Office 365 has recently been installed on my 
> machine (Version 2212 (Build 15928.20216 Click-to-run).
>
> Since then I have started getting errors when I link to SQL tables 
> without using a DSN (basAttachDSNLessTable).  The error is 3125 – 
> "dbo.tblGroup is not a valid name. Make sure it is a valid parameter 
> or alias name, that it does not include invalid characters or 
> punctuation, and that the name is not too long".  I get a similar 
> error for several different databases doing the same thing.
>
> I am wanting to revert back to a previous build of Office to see if 
> this is the problem but am having trouble finding out how to.  I think 
> the one I want is Version 2212 (Build 15928.20198) from Jan 4.
>
> One website suggested this:
>
> To rollback Office to one specific version, you could also try to run 
> following command.
> Such as "C:\Program Files\Common Files\microsoft 
> shared\ClickToRun\officec2rclient.exe" /update user
> updatetoversion=16.0.14701.20226
>
> This was from Dec 2021.  But according to this page (
> https://learn.microsoft.com/en-us/officeupdates/update-history-microso
> ft365
> -apps-by-date
> <https://learn.microsoft.com/en-us/officeupdates/update-history-micros
> oft365-apps-by-date>) the version numbers around that time were 
> Version 2111 (Build 14701.20262).  So I am not sure how that 
> translates to something like
> 16.0.14701.20226
>
> Any pointers?
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
>
> --
> 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

-- 
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com