SaveSetting/GetSetting Under WinXP

[dilettante]

Has anybody noticed that VB6 SaveSetting() seems to be a no-op under WinXP? And correspondingly that GetSetting() results only in the default value being returned?

Seems to work fine under Win2K, 98SE, et al.

I found this disheartening link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnw2k/html/sidebyside.asp

But I doubt it offers a solution aside from coding to the API instead of using the VB intrinsics, which though admittedly limited meet my needs in most cases.

Seems to be talking about Win2K, but I suspect these recommendations may have become mandatory under WinXP.

I get this (no-op) behavior on WinXP even logged on as an administrator.

Any help appreciated!

 

[dilettante]

Hmm...

I guess I have to say "never mind."

Wasn't working yesterday, but it seems to work today.

'Course I did uninstall the program, and then reinstall it again with an application manifest.

But the program failed with the manifest in place, so I renamed it with .sav and now it runs.

I'm stumped. Oh well.

BTW - the application manifest was an attempt to get access to version 6 of comctl32.dll, which you need to get XP visual styles for your controls (command buttons, et al.).

Anybody have this working yet?

With the manifest in place my splash screen form comes up ok, but when I hide it and the main form is supposed to come up, I get some rude noises (literally) and the program just goes away without ever showing the main form.

No error in the application or system logs, no popup error dialog, nothing. Just those rude noises.

When I hide the manifest by renaming it .sav the program runs as expected, but using the version 5 comctl32.dll and the old visual styles in the window's client area. You know, rectangular command buttons and all the other retro-looking stuff.

I guess I need to do more than just have a manifest, huh?