I never realized this until now, as I always had an Admin client, and could utilize the tool there for this… but Now… I am ONLY a Designer… no access to an Admin client. When I need to refresh the design of a database (with changes in a template) it’d be helpful for me to know if anyone is still in the database. We send a notice out… Please exit the database for 30 minutes… but who knows if everyone does? Perhaps as a menu item… you could add: File - Database - DB USers Connected?
Subject: New Feature Suggestion Designers could use…
Ruth,
Agreed, this is a bit of a hassle. I guess the only real solution would be that if the domino server were willing to send a flag indicating that users must refresh their design cache upon refresh.
When I’ve worked with clients under these conditions, I try to have a consistent release day/time, for example, Friday afternoons or every day at lunchtime. I send a message out, even if it’s just to the db owners, detailing the changes, so that at least there is a kind of FYI. It’s not sufficient, I know, but it’s something. And of course I try to limit the frequency of these changes.
regards,
raphael
Subject: RE: New Feature Suggestion Designers could use…
thanks Raphael,That is what we are considering now… a scheduled refresh time. Thanks for your input.
Ruth
Subject: New Feature Suggestion Designers could use…
If you have the authority to perform such commands
Take a peek at: notesSession.SendConsoleCommand in designer help. I think it will do your trick with a bit of coding.
Subject: New Feature Suggestion Designers could use…
I wouldn’t say that the Admin client is more powerful than the Designer. If you are still listed as an Administrator of the server, you can send a broadcast message and drop users from all databases via a server console in LotusScript, automatically!
I’m not sure how useful such info would be that if someone is connected to the database, as I would anyway drop all users, no matter if there are 0 or 100 users connected to the database.
And I’m not even sure if dropping users helps anything, as most users don’t delete their cache.ndk before they start their Notes - they might have ancient Forms loaded in their Notes which don’t update because their cache.ndk is corrupted.
Usually I don’t also manually refresh designs of databases during work hours, I just deploy the changes in the template and let the nightly designer task refresh the designs. Then no additional hassle is needed.
Subject: RE: New Feature Suggestion Designers could use…
Thanks for the reply… 1st - I didn’t say it was more powerful (Admin client) just that it has some features Designers can’t get to if they don’t have an Admin client.
2nd - If I was a member of an Admin group, this wouldn’t be an issue… as you pointed out, and hence i wouldnt be writing about it.
3 - The reason we don’t wait until the 2am Design Refresh is that we are a 24 hour shop, we have offshore people developing at that time of ‘day’ and then we check them out in the AM (our time) and then need to refresh the design, once changes are approved.
But thanks!
Subject: RE: New Feature Suggestion Designers could use…
But but, according to SOX (=Sarbannes-Oxley) you can only update the design about once per week, and you need to have a meeting before each design change, so that all members of the team are informed and approve the changes 
I thought you were withdrawn the Admin Client also because of SOX.
Subject: RE: New Feature Suggestion Designers could use…
Sorry I am late to this Mika, but I am rolling on the floor laughing at this one. And you know why!
Subject: RE: New Feature Suggestion Designers could use…
LOL funny man.
Subject: RE: New Feature Suggestion Designers could use…
Yeah it sounds ridiculous, doesn’t it? But that is really how we have to work according to SOX 