I have a lax management group that gives too many liberties to some of the users of one of my databases. I have gone over to work on them sometimes and found them renamed (how about Shaquille O'Neal?) and other such shenanigans.
Another big problem, which I would like to address today is this. The users will copy the front-end and place it somewhere else, create a shortcut to that one and use it. I have scripts that close that one and open another one. So, when they use their copy the scripts don't work and I get a call. There are multiple users, but one is the primary user on a specific computer. That position has a different person each day.
I have reported these but to no avail. The response is "I know." Does anyone have an idea how to stop this? For instance, when they open the database, and it is not the correct one, I would like to stop it from working, preferably by giving a message and then closing. For example, if DB1 is in C:\Folder1 and they copy it somewhere else and try to use that one, how can I get the database to recognize that the one being opened is not in C:\Folder1? I could do it with a script by letting them click on the script, but I would rather do it internally to the DB.
Is that doable?
Thank you.
Another big problem, which I would like to address today is this. The users will copy the front-end and place it somewhere else, create a shortcut to that one and use it. I have scripts that close that one and open another one. So, when they use their copy the scripts don't work and I get a call. There are multiple users, but one is the primary user on a specific computer. That position has a different person each day.
I have reported these but to no avail. The response is "I know." Does anyone have an idea how to stop this? For instance, when they open the database, and it is not the correct one, I would like to stop it from working, preferably by giving a message and then closing. For example, if DB1 is in C:\Folder1 and they copy it somewhere else and try to use that one, how can I get the database to recognize that the one being opened is not in C:\Folder1? I could do it with a script by letting them click on the script, but I would rather do it internally to the DB.
Is that doable?
Thank you.