Thank you for your post.
The problem with the older versions was that everyone was taking down files, making changes, and relaunching the files. More users wanted tighter security, so for some time now, the Admin Console is the only way to do this. That is, if someone wants to make a change, they go through an Admin. If you have a person who is continually making changes, you may want to consider giving them Admin Console privileges, and/or give them a clone of the file, and when changes are made, the clone is given to the Admin, updated to the server, and the records imported from the existing file into the clone.
Let me know if you need clarification for any of the above steps.
Thanks for your reply. I had a feeling that was the case. Any chance that there's a way to only expose the database admin part of the Console? Opening and closing databases is all they really need (user restricted of course).
Unfortunately, there is no way to expose only the database admin part of Admin Console.
Didn't think so. Thanks, anyways.