Search results

After reading the posts here as well as in other forums it seems that Stored Procedures is the way to go. Our database consultant also agrees that Stored Procedures will resolve most performance issues. So that's the direction I'm gonig to take.

Yes, every table has a PK and each record timestamp.

Looks like I may have to bone up on stored procedures, then.

Understood, pulling this together now. Also, understand that this code works sometimes and sometimes not.

Yes. Data is massaged. Several queries do inner joins to pull in data from multiple tables.

I come again to the Well of Knowledge... Just a question, actually. Since moving our SQL backup from an on-prem SQL Server to Azure SQL, the performance of our Access front-ends has slowed dramatically. We were warned and expected this to be an issue. However, I was not expecting VBA...

I will try that first. My SQL knowedge is rudimentary. But this query did the trick. I now have a correct count for CONWAY. So thank you!

I can as long as the data remains secure and private. It has employee data, obviously.

Six character alpha. In this example, the code is "CONWAY".

I come again to the well of knowledge... I have an anomaly happening with a query that is functioning properly except for one record. I have a table with a list of supervisors and a second table with a list of staff. Each staff record contains a supervisor code that refers back to the list of...

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.