[AccessD] Uninstalling Office Update

David Emerson newsgrps at dalyn.co.nz
Thu Jan 12 22:09:51 CST 2023


Thanks for the link.

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

I have had to deal with these automatic updates by Microsoft causing unintended issues with MS Access several times over the past seven years. I finally got the client’s cloud provider hosting their server and Terminal Server (called something else these days) to turn off automatic updates for MS Office - we only do updates some months after once the various issues that now and again hits MS Access in a bad way is resolved.
So encourage you client to turn off automatic updates - unless you want to be their trouble shooting hero of course - :) - and more often than not you find these updates issues and their hot fix by running a google query. … Here is one link… https://answers.microsoft.com/en-us/msoffice/forum/all/has-version-2212-of-ms-access-affected-attaching/e730184f-db94-4fa8-b144-491c638df87c

.. still reading it myself

/borge

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

> 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-micro
> > so
> > ft365
> > -apps-by-date
> > <https://learn.microsoft.com/en-us/officeupdates/update-history-micr
> > os
> > 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
>
--
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list