Make my front ends automatically update themselves

[Essendon]

Hi all,

I am working on a system that has a back end (on the server) and 6 front ends (all identical, one on each of the client pc's). This means that whenever I make a change to the front end, the updated version of the Front End has to be copied + setup on all 6 client machines. This also means that I have to go on-site everytime I want to make an update. Sometimes I might need to make just a very minor update, and just cannot get onsite to deliver it.

I want to be able to login to the server remotely (using Win 2k Terminal Services) and copy the latest version of the front end to a designated shared folder on the server (I can already do this without a problem). Then each time a front end is opened (on a client pc), code will run to check the designated share folder on the server to see if an updated front end is available. If it is, it will be copied to the client pc and replace the front end the user currently has open. It's filename will be identical so that the desktop shortcut still works and the new front end will then open up so the user can continue working as per normal.

The only problem that I see with the above would be in the closing of the front end, copying of the new front end to the local machine and then opening it back up. I assume that the code that does this would have to be separate from my front end other wise I wouldn't be able to replace the front end file because it would be already in use.

Do you think what I have described above is a good idea for what I am trying to achieve? Has anyone else done anything similar before? Any ideas/comments/help would be greatly appretiated.

Cheers,

Peter

 

[WayneRyan]

Peter,

The front can use the OnOpen event on the main form to look for
a new front end. If it sees one, it can launch either a
VBScript (or .bat file) and then close itself.

The VBScript can pause, or ask the user to hit return, do the
file copy and then launch the new app.

Haven't tried it, but it "sounds" easy.

Wayne

 

[CALV]

ok, I had a similar (actually the same) problem, heres what I did:


Create a logon script for the 6 users in question to copy over the FE from the server to the users desktop REGARDLESS of wether or not a new version exisits, this will ensure that at each logon, the latest version will be on the desktop.

I had a problem with users using an older version, so I did this:

On the FE main form, I put a label with the version number, in the BE, I created a new table with 1 field called version, then when the form loads up, I checked the label.caption against the version field, if it didnt match, it gave an "incorrect version error" and closed the db, as long as you remember to change the lablel, and the version number in the be table, should work a treat - worked for me.

HTH

CALV

 

[Essendon]

Many thanks for your replies.

Hey Wayne (or anybody who can answer), I'm wondering how you can launch VBscript to run on its own? Would I have to add it into another mdb file or can it run by itself somehow? Or am I getting it confused with VBA?

Thanks again.

 

[WayneRyan]

Peter,

You can launch VBScript from within Access. I have samples
at work, but am on medical leave, so don't have samples.
I will find something though ...

You can search here for the Shell command (or even Shell
and wait).

For this purpose, even a .BAT file will suffice.

Either one, will have to pause for a second to wait for the
"old" front end to terminate, then it can do the file copying
and launch the "new" front end.

Wayne

 

[Autoeng]

There is a fine sample on how to do this on www.tek-tips.com right now under the Access - Other forum.