we have interesting problems with Windows 10 in combination with compatibility mode. Maybe someone here has had similar problems or can share some thoughts...
Our main problem is that our program, if run in "Windows 7 compatibility mode", doesn't seem to be willing to load VBA for Word when automated via COM.
If Word is started manually before performing all the COM automatosation, everythings works fine.
So a quick and dirty work around would be to tell the user to start Word manually if this situation is detected. That should not be too difficult, as we could check the difference beteween GetVersionEx (which will return 6.1 if runs in Windows 7 compatibility mode) and NetServerGetInfo (which will always return 10.0 for Windows 10).
Did anybody ever use NetServerGetInfo? It's not in the WinApi-Declarations in the Sample Vault and it seems to be kind of annoying to define. I'll have a go at it but if anyone has a smart idea, I'd be happy to listen.
 https://docs.microsoft.com/en-us/window ... versionexa (yes, deprecated... but still working)
 https://docs.microsoft.com/en-us/window ... vergetinfo
attached is an example to call NetServerGetInfo from Gupta.
It's indeed a bit complicated to call it from Gupta.
[ frevel & fey ] Software-System GmbH
thank you, that's very kind of you.
I have come up with something similar, but as I needed only the version numbers, I didn't bother with fetching the strings as well. Very nice!
Kind regards, Clemens
Who is online
Users browsing this forum: [Ccbot] and 0 guests