Search results

I can confirm that today's O365 update resolved the slowness issue. Thank you all for your assistance.

Thank you all for your responses; they were most helpful. Dropping O365 back one rev level fixed the problem! Looking forward to Tuesday updates. Hopefully they really did fix the issue.

Office 365 apps updated on their own when we added the new PCs to Intune.

Yeah, I did do that. Nothing that screams out at me.

Can't be done. It's been rolled out organization-wide. We don't use Wifi within our building. 2Gb ethernet service.

Interesting you should mention this. Every other launch of Access never gets to the splash screen. I have to go into Task Manager and end the MS Access task. The next launch is normal.

Microsoft® Access® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 64-bit

You guys are the best! Digging into research now!

I come again to the well of knowledge... My shop uses a number of Access front-ends. All are connected to various DB instances on a SQL Server. They have been running pretty much faithfully for 10 years. Over the past couple of weeks, though, response time on all of the front-ends has been...

In eleven years, this has never happened. But I will take your suggestion under advisement. Yes, the Dim state is DAO.Database; I just didn't spell it all out.

OK, following your suggestions, I learned that the TILLDatabase variable is, in fact, Nothing. Somewhere in the midst of processing, TILLDatabase lost its value. Now I need to trace where this happened because it definitely should not be. The only place where I explicitly set it to Nothing is...

It is. It's a Public Dim It's used in multiple Subs and Functions throughout my app.

Dim TILLDatabase as Database

I put the breakpoint at the beginning of the sub. The error got thrown when I stepped into the DELETE statement.

Private Sub PhoneBook_Click() On Error GoTo ShowMeError ProgressMessages = ProgressMessages & "Updating Phone Directory." & vbCrLf: ProgressMessages.Requery TILLDataBase.Execute "DELETE tblPhoneDirectory.* from tblPhoneDirectory;", dbSeeChanges TILLDataBase.Execute "INSERT INTO...

This is an SQL statement executed within a VBA module. This statement has been executing without fail forever. It just started doing this today. I could understand if this happened because of a missing field, but a DELETE statement??

I come again to the Well of Knowledge... I have dealt with and resolved "Item not found in this collection" errors before. This is a new on me because it happens when the SQL statement "DELETE tbl.* from tbl" command. What would cause this on something as simple as a DELETE statement...

The DB has been compacted, repaired, then uncompiled and recompiled. Yes, everyone has their own copy of the front-end. I uninstalled and reinstalled Access Runtime 2016...no love. I even uninstalled Runtime and installed full Access 2016...still no love. I'm completely baffled.

This doesn't seem to be relevant. We're running Access 2016 (and 2016 runtime), legacy installation (not click-to-run), we are not a 365 shop. Our Access 2016 is fully patched.

Greetings to the well of knowledge... Posting this as a general question as I really don't think I'm dealing with a true corrupt query. I have an Access front-end to a back-end SQL Server DB. I make periodic updates to the front-end, on about an every-two-weeks basis. After the most recent...