boblarson
Smeghead
- Local time
- Today, 10:14
- Joined
- Jan 12, 2001
- Messages
- 32,059
Actually he doesn't most of the time, but since we work together, at the same location, I had told him of your post.
Bob Larsons FE Auto Update Utility
- Thread starter olorin
- Start date
Hey Bob,
I know it was been a few years since this thread has been active, but I am wondering if you were able to modify your auto update utility to work for multiple frontends? I have been using FE Auto Updater by Access MVP Tony Toews which work wonderfully for the past few months but our IT security has been increased I am not able to save executable files to our network shared folder. Your utility seams to work just as great, but I would like to have one table that houses all of the various frontends and have your utility code DLookup the version number if the database names match.
I know it was been a few years since this thread has been active, but I am wondering if you were able to modify your auto update utility to work for multiple frontends? I have been using FE Auto Updater by Access MVP Tony Toews which work wonderfully for the past few months but our IT security has been increased I am not able to save executable files to our network shared folder. Your utility seams to work just as great, but I would like to have one table that houses all of the various frontends and have your utility code DLookup the version number if the database names match.
boblarson
Smeghead
- Local time
- Today, 10:14
- Joined
- Jan 12, 2001
- Messages
- 32,059
I have not done anything like that. Theoretically you could just build a master database which then you would link both the table from the backend to the master and the table from the frontend to the master. You would rename each of them in the master database (you can do that and not affect anything). Then you could just change the version numbers there and not go into the backends or the frontends. Does that make sense?
Thanks,
I should have just stepped away earlier and then came back. I actually modified your Dlookup to simply add a criteria based on the currentproject name and also added a field in the back-end version table that identifies what database is currently using what version. Keep in mind I did this like 4 hours ago and have been trying to figure out why it wasn't working. The reason it wasn't working for me is beacause I did not notice that the modules FEUpdate and General did not copy over into the second FE database. Once those were inplace my modification worked like a charm. Thanks Bob for creating such a great utility so that I can slap my IT department in the face for blocking me out of the previos utility. LOL
I should have just stepped away earlier and then came back. I actually modified your Dlookup to simply add a criteria based on the currentproject name and also added a field in the back-end version table that identifies what database is currently using what version. Keep in mind I did this like 4 hours ago and have been trying to figure out why it wasn't working. The reason it wasn't working for me is beacause I did not notice that the modules FEUpdate and General did not copy over into the second FE database. Once those were inplace my modification worked like a charm. Thanks Bob for creating such a great utility so that I can slap my IT department in the face for blocking me out of the previos utility. LOL
