Recent content by Marshall Brooks

Waiting to hear back from my users. I know in the past, I've done the same thing and not had the sluggishness I initially reported. And our local users, didn't report it, only the Citrix users. And what I did earlier probably would NOT fix it from what @NauticalGent says - i.e. I ran the...

At this point, I'm not sure if it was the Powershell script or the Trusted Publishers update. Apparently, both were done before I re-tested.

Something happened, b/c this database was never on the internet nor sent via E_mail, but running the PowerShell script resolved the issue.

@isladogs - We distribute via a network drive. I never saw the Unblock text or checkbox under Properties - even when I was having the issue, but I ran the Powershell script and it seems to have fixed the issue (for me, at least). I ran the unblock on my shared folder and then copied it to the...

MOTW was apparently the issue. I was skeptical b/c I didn't see an Unblock option on the Properties menu, and the Powershell script didn't give any confirmation, but I ran it and everything seems to be working okay. I only ran it on the FE, but that seems to have worked. Question: If I run the...

No and that seems likely to be the issue. From the Front-end or the back end or both? And how do I do that? I was having issues with Excel files also and it ended up being an issue with having protected view enabled, but one suggestion was copying to a local folder and checking unblock. The...

@isladogs - Thank you. That SOUNDS like it could be the issue, but there are some significant differences in my case. First off, in the trust center>Macro settings, by default we are using this option: "Disable all macros with notification." I think we have the ability to change it to enable...

Follow-up. It seems to be mainly my VBA code that is running slowly. I'm guessing this is more likely related to Office 365 than Server 2022. I tried to compare between my local and Citrix settings, but is there something besides Trusted Locations that would slow down VBA code?

Citrix admins have not changed. They do admit that they don't know anything about Access and its set up. See above for Windows and Office Versions. Citrix was using Server 2016 and Office 2016 and was fast. Citrix is now using Server 2022 and Office 365 (and different virtual servers) and is...

Basically, I stopped using VPN - for speed reasons rather then potential corruption, but I understand your point. I used Citrix when I was working remote b/c it was faster. It still is for queries and record access, but it no longer is for my VBA code.

I don't understand exactly how with works, but I shouldn't have implied we were using the VPN over Citrix. To try to re-word: Locally (non-Citrix), the database is a lot faster in-office than it is over VPN - but the main slowdown seems to be opening queries and tables, rather than running...

Follow-up: I had to use the database this morning after adding the back-end folder as a trusted location and it was still painfully slow. I'm in the office today and not using VPN, so it is not VPN related. Then again, it wasn't before - i.e. previously it was fast whether I was using VPN or...

@Minty - Thanks, I'll try that. Stupid questions time: That would have to be set for each user, correct? Stored in their profile or else by group policy. Trusted locations for the front end or the back end or both? We had to set Trusted Locations for the front end or the database wouldn't...

@Pat Hartman - Okay, thanks for chiming in. I'm puzzled by the slowdown b/c previously we were running Win 11 and Office 365 locally and Server 2016 (Win 8) and Office 2016 on Citrix and Citrix outperformed the local installation. I would have expected running a common version of Office (O365)...

To clarify and give more information. The database initially loads slowly over VPN. That still occurs. It still loads quickly in Citrix. What is no longer working quickly in Citrix is some of the VBA procedures. Copying files, generating pop-up messages, etc. Those used to run quickly but now...