If you are updating a query, form, or report (and not the data) on a front-end that you would like everyone to have, you will have to re-distribute the front-end to your user group.
Here is how I make sure everyone has the latest copy automatically at my office.
I keep a copy of my current front-end on the network, with a version number on it (with each update, I update the version number). I then created a batch file on the network that copies the front-end over to their hard-drive, and then launches it from there. Actually, the batch file checks to see if they already have the latest version on their hard-drive. If it does not, it copies it over then opens it up. Otherwise it just opens it up on the hard-drive. I then place a shortcut to the batch file on their desktops, and this is what they use to open the database.
So whenever I do an update, I just need to update the version number on the front-end database name, and update that version number in my batch file.
A co-worker does something similar, but a little easier. His batch file just copies the front-end database from the network over to their hard-drive every time and opens it up. That way, you don't need to worry about maintain version numbers.
As long as the users only open the database using the batch file shortcut we put on their desktops, it works pretty seemlessly.