Updating the FrontEnd - New Version Control with ADP & ADE file formats

  • Thread starter Thread starter WhatTha
  • Start date Start date
W

WhatTha

Updating the FrontEnd - New Version Control with ADP & ADE file formats

With the MDE & MDB file formats We have been able to use normal
updateder code to pull the latest version of an mdb or mde FrontEnd to
all my client desktops - to avoid having to do this one desktop at a
time... works great

But NOT with the ADP or ADE project file formats...

Has anybody got any code or instructions or websites on how to do the
new version updating with the ADP & ADE file formats...

The mdb/mde code just doesn't work no matter what we have tried with
our limited brains...

thanks....

cj...
 
I usually setup the client workstations to execute the program by running a
command file that always copies the latest FE version to their local
computer and then executes that local copy. So deployment is just putting
the updated file on the server.

Something like this:

copy /y "\\Server\ShareName\FrontEnd.mde" "%HOMEDRIVE%%HOMEPATH%\My
Documents\FolderName\FrontEnd.mde"
Start "ArbitraryProgramCaption" "%HOMEDRIVE%%HOMEPATH%\My
Documents\FolderName\FrontEnd.mde"

Paul Shapiro
 
Paul,
I appreciate you taking the time to answer but we have never had a
problem doing a MDB or an MDE auto Update but we have NOT found a way
to do this with a ADP or ADE - so it is with that file type that we are
having a great challenge...

any other thoughts would be very appreciated...

cj...

****************************************
 
What is "normal updater code"? What's its name? How did you come to
have it? Was it included with one of your applications?

You might google the Access newsgroups for "Tony Toews". Get his URL
from his signature line. Go to his site and search on FE Updater.
Modified versions of his code are running everywhere. That will show
you the model of some working code.

It stands to reason that a desktop utility or script could compare
dates, say the file creation dates of the local front end and the
master copy on the server. When the server s date is newer, delete
the last saved copy of the front end, rename the local front end to
save it, download the new version, run your application.

I doubt that the above was much help but you'll probably have to come
up with a lot more specific information to get specific help.

HTH
 
Back
Top