Question : Auto replicating

I have a front end and a back end, split database, that I replicate.  Reason for replication is the front end is being changed all the time that I hated having to have the user copy the replica down to there desktop after I made a change.  So now when they log in and open the application it replicates everything but the tables.  So far my time spent on fixing corrupt tables is down to maybe once a month if that at best.

Would it be wise and can I do it to replicate while the user is using the application?
I can see that what if I made a change to a form that a user had open.  Would they get the change or would there be a conflict?  It's just an idea I am floating.  I had to create a shutdown form so user that leave it open when I need to make a change to the backend at night will be logged out of it.  However not all user have that form yet as I created it an hour a go and they will get it in the morning.  But I have two users whose offices are locked and I need to make some changes to the tables and can't because they have it open.  The real question is can I auto-replicate and what are the pros and cons?

Answer : Auto replicating

First and foremost: You should NOT use replication to deploy changes to your FE objects. Replication was intended to work with data, not objects, and while it _technically_ works, it's not the correct platform. I don't use replication, but know several very experienced Access devs who do, and every one of them say the same thing - don't replicate objects, only data.

If you need to deploy changes to the FE, then just have the user download a new copy of the FE when needed. You can create an "auto-update" feature to do this, or there are several utilities like this around the 'net (http://autofeupdater.com/). Include relink code to link back to the BE and you're done.