Charles,

I'm not sure I can tell you the exact logic it uses I've never been able to completely figure it out. You might take your foxuser and put it in a safe place where VFP can't find it and let VFP start a new one from scratch and see if it helps.

>Yes, foxuser is the resource. I opened method code window, set the values, saved the window and the class. Reopened and the value was saved. Did the same and escaped out and the value was not saved. So for this seemed not too bad. Went back in and started opening differnet code windows and noticed that sometimes the previous setting was present and sometimes was not. Thought maybe the setting was window specific, or baaseclass specific, not that I understood why it would be that way but hey, it was worth a try. The bottomline was that there was no visible logic to when a setting was kept and when not.