Hey all,
I've been pouring through hundreds of forums recently and finally decided that I should get in on the action.
I am trying to update some forms and reports, also some minor back end changes, to a database that is shared by approximately 20 people. I make these updates every 2 weeks or so. How the database is set up is that there is a front end and a back end on the network. All of the users create their own shortcut to the frontend and place it on their desktop. I am at a plant that runs 24/7 so the database is always in use, making it difficult to simply change any objects.
Thus far I've been simply creating a copy of the front end, making all necessary changes, then putting the new version back onto the network and emailing the users telling them to remove their old shortcuts and create a new one. This works, but the users are getting annoyed with constantly having to update the version. and rightfully so.
So I was hoping you guys (and girls) could help. I've been reading about exclusivly opening the db however I wasn't quite sure what the reprecutions would be and if that was even an applicable application in my situation. I want it to be where the users can keep one shortcut on their desktop, then have me able to seemlessly update the database whenever I need to. Is this even possible, or am I just dreaming?
I hope I've painted a clear enough picture of my problem. If you need any clarification please ask. I trust you guys can help.
Best Regards
I've been pouring through hundreds of forums recently and finally decided that I should get in on the action.
I am trying to update some forms and reports, also some minor back end changes, to a database that is shared by approximately 20 people. I make these updates every 2 weeks or so. How the database is set up is that there is a front end and a back end on the network. All of the users create their own shortcut to the frontend and place it on their desktop. I am at a plant that runs 24/7 so the database is always in use, making it difficult to simply change any objects.
Thus far I've been simply creating a copy of the front end, making all necessary changes, then putting the new version back onto the network and emailing the users telling them to remove their old shortcuts and create a new one. This works, but the users are getting annoyed with constantly having to update the version. and rightfully so.
So I was hoping you guys (and girls) could help. I've been reading about exclusivly opening the db however I wasn't quite sure what the reprecutions would be and if that was even an applicable application in my situation. I want it to be where the users can keep one shortcut on their desktop, then have me able to seemlessly update the database whenever I need to. Is this even possible, or am I just dreaming?
I hope I've painted a clear enough picture of my problem. If you need any clarification please ask. I trust you guys can help.
Best Regards
Comment