Has anyone observed this issue with Shared Values in Vista?
In XP:
if you set a shared value and then exit the app, the value/stringremains.
In Vista:
if you set a shared value and then exit the app, the value/string goes away.
Printable View
Has anyone observed this issue with Shared Values in Vista?
In XP:
if you set a shared value and then exit the app, the value/stringremains.
In Vista:
if you set a shared value and then exit the app, the value/string goes away.
I havent noticed it but have noticed it staying in xp, ill have a test on vista in a min but i guess its something to do with the way the OS manage memory, am i correct that shared values are stored in the ram? - that should be correct. Maybe vista has some new way to record and remove data from the memory when an application starts or ends? (btw do you mean with the shared data object?)
Yes, the shared data object.
What you said makes sense.
No I have just tested it and the value still stays as it was (in vista). It should free the memory once the application ends, but it doesnt, which should indicate a bug in the object.
Correct there is a bug in the object, it doesn't free correctly the handles used by the object. The programmer must have read the MS documentation too quickly. It will be fixed in the next build, i.e. the values won't exist anymore if you run the application again.
OH! THIS line makes me a happy guy:
"It will be fixed in the next build"
:D