Updating Interface

[gary.newport]

I have an Access file that is simply the data tables and this is in a fixed location (s:\data, with the name data.accdb).

I have an interface file that can be copied by any and all users anywhere they wish (called interface.accdb).

I am making changes to the interface and will continue to do so, therefore I have been working on a deployment tool that works like this:

• interface carries version number and link to data table, which contains latest version number. If these two differ then an upgrade is implemented
• The old interface opens an update file (an Access form and a tiny amount of VBA) and closes itself
• The update file copies the new interface over the old interface, then opens the new interface
• The new interface has the same version number as the data file implies and so the new interface opens up as normal

Now the issue is that the interface file can be anywhere so how can I parse to the update file the location of the calling file (the old interface file) and so let the code know where to send the new interface?


I could use the data tables and yet what if two people wish to update at the same time? I could potentially end up with mis-information.

 

[BlueIshDan]

Funny thing, I was just preparing my system, that works exactly like you described, for posting to this forum.

It contains a version file that sits one each the users and the servers location. These the users file parses the server file to keep up to date with its version numbers. I private message me if you would like a quick copy of this system.

Regards

 

[BlueIshDan]

Funny thing, I was just preparing my system, that works exactly like you described, for posting to this forum.

It contains a version file that sits one each the users and the servers location. These the users file parses the server file to keep up to date with its version numbers. I private message me if you would like a quick copy of this system.

Regards

Oh my lord, reading over that mad me laugh. Early in the morning and I clearly can't say anything right! You get the just of it though

 

[Frothingslosh]

I'm surprised you two are re-inventing the wheel. Self-updating routines are fairly easy to find ready-to-go via Google. In fact, someone else was commenting on one that we eventually got running for him in this very forum last week!

 

[BlueIshDan]

View attachment update system extraction.zip
Here is the extraction from my project. If you're unable to read through and figure it out enough to be able to modify the file and the code to suit your needs, I will be more than willing to help.

The way it works:
You create two objects based off of the update file class that I have created.
One loads the local machines version file, the other loads the server's.
The local machine version file then compares itself to the server's version file object. You can compare multiple version types, depending on how you set up your file.

The code should tell the story itself