[AccessD] Office 365 update issue ?

Jeff Barrows jeff.developer at gmail.com
Tue Dec 3 14:49:36 CST 2019


Go online, the query issue is a known problem and the fix should already be out. I had the issue last week with half of my Office 365 installs.  Check to see if there is an update available from within MS Access.

Thank you,

Jeff Barrows
jeff.developer at gmail.com

-----Original Message-----
From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of Mark Simms via AccessD
Sent: Tuesday, December 3, 2019 2:27 PM
To: accessd at databaseadvisors.com
Cc: Mark Simms <mar.ko at verizon.net>
Subject: Re: [AccessD] Office 365 update issue ?

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




More information about the AccessD mailing list