How to stop "restrict/allow" visibility or renderability from resetting

Good evening,
Does anyone know how to stop "restrict/allow" visibility or renderability from resetting automatically when I close and reopen a file? Please let me know.
Thanks,
Scooter

I suppose I'd need a more specific instance in how or when this happens so that I can try to recreate the problem from my end.  Other than that I'd be stabbing in the dark.

Good evening,
When I am in a file and when I "restrict visibility or renderability" on particles using the outliner then close the file, they will be automatically turned back on next time I open the file.
Thanks,
Scooter

Ok, please excuse my ignorance here because I'm sure that I'm missing something.  I set up a "test" file with a particle system, saved it and closed out.  I opened it back up and then went into the outliner and turned off renderability.  At this point there's two things that can be done, either save and exit or just exit.  When I saved it and then came back to it, it was still set to off.  When I just closed without saving and came back it was of course on.  As far as I can tell mine doesn't undo what I've done after saving.  Are you using an earlier version, or am I just not getting it?

Good evening,
I am sorry, I failed to provide enough detail again. I am working in a scene with linked sets and characters, so if you made a new file and linked your test file that has the particles into the new file then try restricting renderability in the new file, save, close and reopen, that is where you may experience what I am referring to.
Also, I am using version 2.58.
Thanks for looking.
Scooter

Ok, figured it out.  When I link a particle system file to a new file and that particle system is set to renderable then you will see it that way in the file that you linked it to.  I'm guessing that's because the file that it is linked to is "gathering" that information from the latest settings within that current particle system file.  If I go back into that original file and save it as non-renderable then it reflects that change in the linked file.  I didn't test to see if it did it dynamically or not, but it works by opening and closing one after the other... another words, I don't know if it will change it on the fly.  BTW, I'm using 2.67b.

Thanks for looking.
Scooter