anyone had the vb /vba (savestetting) registry keys disappear in windows 10? presumably after some update
do i now need to use some other registry key for safe keeping of paths?
seems to have happened to at least 2 machines on one site
Printable View
anyone had the vb /vba (savestetting) registry keys disappear in windows 10? presumably after some update
do i now need to use some other registry key for safe keeping of paths?
seems to have happened to at least 2 machines on one site
I haven't seen that. Can you track down the update? Even the date when the update was applied might help a lot. I assume it was recent, perhaps since Redstone 1 started being pushed out?
I long ago gave up on those registry keys myself, since Microsoft is pretty adamant that settings and random data should no longer go into the registry. That was the strongly worded suggestion back when Longhorn was first released as Windows Vista, and I haven't seen any reversal since then. They recommend persisting to files in a folder created for your application within the user's profile, using XML or INI but any format you want (even VB's Write/Input "CSV" format) works fine. Whether you choose the local or roaming profile depends on the situation of course.
But if you are seeing this occurring I doubt it has anything to do with that philosophy change. It shouldn't be happening in any event.
Crazy notion: Does installing Office (or a new version of Office) ever wipe the entire bunch?
no that i know of, and i have done that a few timesQuote:
Crazy notion: Does installing Office (or a new version of Office) ever wipe the entire bunch?
1st noticed yesterday, was working friday, but i am not sure if an update even took place, just seemed most likely causeQuote:
Even the date when the update was applied might help a lot.
i doubt there were any other keys, i only used for the database path on network, only the one key, i thought of changing to some file or other current user registry key, but have made no decision as yet, just exported the registry key in case it happens again, though of course may never do so
the other issue that appeared when they updated to w10, was that i had to add a \ to the path in the registry, though it had not been necessary previously, something wrong in my code that had not shown up before
i did have some issue when updating to windows 10 that users settings would be missing after reboot and have to do again