[AccessD] Office 365 update issue ?

[Mark Simms]

Thanks enormously for that Rocky.....The article pointed to another article on how to revert to previous Office 365 versions....and how to shutoff automatic updates.

Mark Simms
marksimms at verizon.net


-----Original Message-----
From: rockysmolin bchacc.com <rockysmolin at bchacc.com>
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Sent: Tue, Dec 3, 2019 4:58 pm
Subject: Re: [AccessD] Office 365 update issue ?

Maybe this will help:

https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec

https://tinyurl.com/udosljf


Rocky Smolin
Beach Access Software
760-683-5777
www.bchacc.com
www.e-z-mrp.com
Skype: rocky.smolin
 


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Ryan W
Sent: Tuesday, December 03, 2019 12:56 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Office 365 update issue ?

query is corrupt is a patch that came down that was faulty.... you gotta
back it out.


On Tue, Dec 3, 2019 at 2:28 PM Mark Simms via AccessD <
accessd at databaseadvisors.com> wrote:

> Well the errors keep building....users now getting a 3340 error "query is
> corrupt" in a procedure that has not changed for years...as well as the
> UPDATE query.I need help on doing a rollback of some office 365 updates
> that obviously have occurred recently.Windows 10 environment. (Remember I
> had the problem with the database corruption that was resolved by a
> registry fix...Windows 10 only)Is it possible these new errors are also
> specific to Windows 10 as well ?
> Mark Simms
> marksimms at verizon.net
>
>
> -----Original Message-----
> From: Jim Dettman <jimdettman at verizon.net>
> To: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Cc: Mark Simms <mar.ko at verizon.net>
> Sent: Mon, Dec 2, 2019 9:24 pm
> Subject: Re: [AccessD] Office 365 update issue ?
>
> Actually not what I thought after re-reading.  Failures of auto numbers
> have occurred in the past. Sometimes a form of corruption.    You’ll need
> to reset the auto number value.
>
> Jim
>
> Sent from my iPhone
>
> > On Dec 2, 2019, at 9:08 PM, Mark Simms via AccessD <
> accessd at databaseadvisors.com> wrote:
> >
> > VBA code that was working for over 4 years suddenly threw an error last
> week.It was basically adding a new record into a table whose primary key is
> ID (autonumber).A duplicate key error message is being thrown (3022).Has
> anyone encountered this problem ? A compact and repair on the back-end
> database did not resolve the issue.I have confirmed with the client that
> they are subscribed to Office 365.
> >
> > Mark Simms
> > marksimms at verizon.net
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

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