This usage of the form as a settings source is probably not an ideal solution to your task as described. I would create a separate class which is instantantiated at start up and can be referenced as class.property. You can then have your form for making the changes 'on-the-fly'. In reality you...
I'm just amazed at how expensive car insurance seems to be in the USA, compared to the UK.
I realize, of course, that what is posted here and my own experience are a mere microcosm of the whole picture.
Sorry to take so long to respond but I realize I will have to describe the basic manner in which all my databases work and I'm trying to devise a reply that is shorter than War & Peace. Wii reply in full in due course.
Actually I find having a 'flag' on a record useful quite regularly and it allows extra flexibility in my search dialogs. As for resetting I automatically clear them when I close down the databases Suits my way of working as I always have a search facility on main listing screens.
I had a similar problem with my library database which I solved by adding a 'flag' field to each record and using the filter criteria to set the flag, then filtering on the flag setting.
Works well as long as you subsequently remember to reset the flag, of course
Back to the basis of IT security - it doesn't have to good but good enough. For instance, we are told 'never write your passwords down', but a physically secure bit of paper cannot be hacked and is certainly better than my memory. The stricture about writing them is aimed at the post-it note...
I love these simplistic debates. They nearly always ignore consequences (and harsh reality).
And I promised myself I wouldn't contribute to this sort of thread again ... sorry.