Updating design changes to a Multi-User Database

[CoopEng]

Hi 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

[CoopEng]

I thought I might include that I'm working with Access 2003.

Thanks again

[Minion]

I'd have to look into a little further for the specifics, but you're already half way there as I understand it. By duplicating the front end and making your changes you're allowing the users to work without interuption. Now what you need to do is (assuming the new front end is the same name) kick all the users out of the db for a moment and rename the old front end (ie. Frontend_Old). Now all you should have to do is copy the new front end over the old and all should be good.

I know there is a way to do this if you're a owner, but I don't have it at my finger tips and I'm running late for a meeting. Still if you can get all the users out this should work for you.

Hope this helps.

- Minion -

[CoopEng]

Minion,

Yeah that's a great start. The plant that I work at has 'down days' where there's is little to no data entry for about 6 hours. Do you know of a way that I can 'kick off' all the users from the database remotely. For instance I send out an email to everyone saying that the database will be down from say 10am - 10:15am. Then I click a button (or whatever this function is) and all of the open instances of the database become closed.

Is there some code that I would have to write for that or is it easier than that?Simply go to 'exclusively open' the database? would that be sufficient? or possible just delete .ldb locked version of the database?

Thanks again Minion, hope your meeting goes ok