Hi Schwartz, thank you soo much for your kind and prompt reply. The set up is to have users on the net from all around the world logging into to my software, which will have LuxCal embedded, for their use. Some users will be their only admin, while others may share that responsibility, hence my noticing this issue yesterday while I was testing. The program (an saas) for now, is not released. I will be proud to notify you folks at that time.
So in a nutshell I just want to make sure when I am logged in as admin, that others will not see the same screen and hence be able to manipulate it (on purpose or mistake). I noticed this yesterday, hence my question.
However I prol should have researched a little more before asking here, but it was late yesterday.. you know 
Anyway I realized a few minutes ago that if I jus go into the sqlite file that I can do everything without logging into another session, and thereby, for the most part, avoiding this possible 'race condition' with the calendar settings.
As far as my initial concern about this, for future (protection) for my users/clients, I suppose what you mentioned should suffice; ie, it will ultimately be up to my clients to assigning admin rights and such, and therefore under normal conditions, this should not be a worry.
My example I suppose of a 'possible' scenario, where someone would be working in the admin screen, at the same time others were 'logged' in and thereby see the admin screen as well. To avoid this, it is now good to know, that I can adjust anything in the db directly, which should be suffice, for safety.
John
All fields with bold label must be completed before the form is submitted.
