Access Updater

For the front end, I would suggest working with a split front end that you make your updates on, not working with an unsplit and then trying to get that front end out into a split environment, the whole scenario sounds like a headache. You're probably going to need to split it again to send out the front end, and then make sure the table locations get updated to the "current" backend that you're using in the environment.

Now the next question, when you say "retain the back end tables". Did you make changes to your tables in your still unsplit version? if so, to avoid data loss you'll probably have to import the changes into the backend that's already out in the environment. Assuming it's in use currently.

Once you get this squared away and are working on a normal split front end for updates next time. Then the access updater is GREAT. Even if you only have a few machines it saves so much time, I know for me we have about 30 workstations and I'm on update version 96.

The thought that I would have had to go to 30 workstations, 96 times, and change out their front end makes me sick to think about LOL. The updater is a life saver worth every penny.

Heck, I only use it on TWO workstations, but I make like 15 changes a day. I wouldn't even want to have to copy that file ONCE. I wrote the Updater mostly for MEEEE!!!! haha