Solved Windows 11 Slow Opening Forms

[MattBaldry]

Hi all,

I have just upgraded to Windows 11 at work and now my forms are really slow when I open them. If I close them, and reopen, they are fast.

Has anyone else experienced this at all?

~Matt

 

[Minty]

Make sure your trusted locations within Windows are correct.
It can cause issues.

 

[MattBaldry]

Make sure your trusted locations within Windows are correct.
It can cause issues.

Hi Minty,

Just added them, but no dice. It takes 9 seconds to open the form first time. Less than a second the next time I open it.

It is only on the Windows 11 machine. I use it on Windows 10, perfect.....

~Matt

 

[isladogs]

I don't have Windows 11, so can't give specific advice but two things to check:
1. If its a split database, check you are using a persistent connection.
2. Also check your cache settings in Access Options

 

[MattBaldry]

I don't have Windows 11, so can't give specific advice but two things to check:
1. If its a split database, check you are using a persistent connection.
2. Also check your cache settings in Access Options

I have tried all that, nothing works. I have also noticed that some of my combo boxes no longer autofill when I start typing. It is not all of them, but they are all built the same. It is very weird. Windows bloody 11

~Matt

 

[Jason Lee Hayes]

I had the same issue but only when running Windows 11 via BootCamp on MacBook. If this is the case i think i can help...

 

[MattBaldry]

Hi All,

I have figured this out. The ODBC driver to Sage Accounts on Windows 11 is worse than ever. When I remove the link to the Sage tables, it is fast again.

I will work on a better method to tie into the crap that is Sage.

~Matt

 

[Minty]

Ah, that old chestnut.
It really is the "Worst ODBC connection known to man" as far as I can tell.

I haven't tried this but it did occur to me as a possible workaround.
Using a separate database link the tables in that, then create queries or links in your main db, to those other DB's tables?

 

[Pat Hartman]

You can't link to a link. You can try the method of embedding the table name in the query so you don't need a linked table at all.

 

[isladogs]

You can 'import' a linked table which appears as a link - I do this regularly

 

[Pat Hartman]

I didn't say you can't import the link, I said, you can't link to the link which is what the OP said he wanted to do. Try it, if you select link as the option, you will not see any linked tables. You only see the local tables in the BE. If you select import, you see both local and linked tables.

 

[isladogs]

I don't see any mention by the OP of wanting to link to a link and I'm well aware that you can't do so.
I gave the solution.

 

[Pat Hartman]

Colin, originally I was referring to Minty's comment, not yours.

Using a separate database link the tables in that, then create queries or links in your main db, to those other DB's tables?

 

[ListO]

I had the same issue but only when running Windows 11 via BootCamp on MacBook. If this is the case i t

hink i can help...

I am having that sort of problem on a VM, although I'm using VMWare Fusion.
What do you know about this slowdown?

 

[Jason Lee Hayes]

Are your using VMware Fusion for a specific reason or simply because the Pro version is now free? Only reason i ask is because VertualBox is also free and may resolve this problem. Personally use Parallels Desktop and no issues there. PM me if you require PD FOC

 

[CJ_London]

I am having that sort of problem on a VM

Also check the memory allocation to the VM - I use virtualbox with 8gb assigned to the VM

 

[ListO]

I'm using VMware Fusion because it worked the best 10 years ago, and up until VMWare was purchased by another conglomerate, they had excellent customer service. I know times change, but I forgot to.

I did increase the memory allocation to Fusion, and it improved quite a bit, but it's nowhere as fast as it is on my old breaking-down MacBook Pro running Fusion. The new Macbook has 10x the power, to no avail. Particularly, it is slow to redraw forms. Instead of flashing onto the screen fully complete, the forms open up blank then visibly populate down the screen. The calculations and behind the scenes actions feel faster, but graphics chug along.

 

[AHeyne]

@ListO : Your problem is that forms open too slow, correct?

- Does this also happen when the form is not bound to any data (table/query)?
- Do you have any code in form-Open and/or -Load event procedure(s) which could cause this behaviour? Try to skip those code and test.

If it only happens with data binding: From where does the data come?
- From local Access table?
- Or from Access table located on host or network?
- Or from SQL Server which runs on host or network?

 

[ListO]

Those are all excellent questions, which i've been asking myself.
The sluggishness DOES act as though the data tables were on a slow server in Ashgabat, but they really are here on my laptop:
C:\CueMaster\Tables\Essex 2

The "C:\" is the virtual drive within the VM. I don't suppose this would work any differently if it were in nested deeper- under "Users" or so?

If I look directly at any of the larger tables in the back-end, they instantaneously appear.
I don't know how to look at a form without the data attached. When I bypass the form-open code, it doesn't open properly either.

THE OTHER telling example of this weird slow-down is that when I open the VBA editor, it populates very slowly. I can see the class objects ripple down the window.

I don't think it's a problem with the code, but with the connection between Access and the operating system, so I just wondered if others have experienced this kind of slowdown.

Funny thing is that when I first opened the database when Windows 11 had just been installed, the speed was very fast.

 

[AHeyne]

THE OTHER telling example of this weird slow-down is that when I open the VBA editor, it populates very slowly. I can see the class objects ripple down the window.

If I understand this point correctly the windows of the modules in the VBE open visually one after the other and that takes some seconds over all?

This behaviour I know well. The VBE will open all windows that have been opened in your last session. If that are many it takes some time.

What I do then is the following:
1. Edit something in any of the modules, so that at least one module is unsafed.
2. Close all windows in the VBE
3. Now compile your code by the menu function 'Debug / Compile'.
4. Now save the project, e.g. by the menu function 'File / Save'

Now close Access and reopen the database. When you now open the VBE it should be open instantly.

Perhaps this optimization will help with one of your other problems.