I have some VB6 applications which have run well under every version of windows since XP. Now we are going over to Windows 10 x64 we are finding our our GUI application is very slow especially in SQL operations etc. We run all applications elevated and played around with various options in the compatibility tab but nothing stopped it from being laggy.
Recently i have found a huge improvement if i run the compatibility troubleshooter. the first time we test it fails because we then have to retry with the admin rights but then it seems quite good.
What i dont understand is what the troubleshooter is doing differently to manually selecting options and also even though i then tell it to save the settings, the next time the application runs its laggy again and we run the troubleshooter. I've done a little research and can confirm the applications are all run from the local hard drive. We also keep the database on the local drive.
Just in case it helps, Running different builds of Win10 from Anniversary to a clean install today of Fall Creator. The Visual Studio IDE is installed under the Program Files directory (not program files x86) and i deselected the ADO, RDS ODBC providers as suggested somewhere on the internet (there are ADODB calls could this have anything to do with it). The IDE runs also with elevated permissions.
There are essentially 3 applications with 2 running in the background. All reference a couple of DLL files from a 3rd party and run several SQL calls to a local database. We have noticed if the database is being accessed elsewhere (even through Access so not repetitively) this also slows down the GUI. This system need to perform realtime tasks and so this laggyness is affecting the operation.
Thanks in advance for any suggestions
The correct, and fastest, latest software to run a VB6 program is only found in the "Windows 7, (SP3)" modes, with elevated (Admin) permissions. Since that version, there have been many safety features added to windows, which have to be "emulated", in order for VB6 programs to operate within certain safe limits. The cost was speed, nearly half the speed, which is measurable with most time-demo codes.
Setting compatibility mode to "Windows 7, (sp3)", and elevating your program to (admin), will return your program back to normal speed. Actually, it will be faster than it was on that version of windows, but only in some areas.
This should be done manually, or at the point of install, of your program. You have to add registry keys, based on where the program is installed and how it is named or identified. Prompting the user so they can OKAY the elevated (admin) access for your program.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With