Auto-update frontends???

  • Thread starter Thread starter Guest
  • Start date Start date
Jeff Boyce said:
Other approaches are available on searching, but this gives you an idea of
how it can be done.
Click to expand...

Actually there are links to other approaches right on that page near
the bottom.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Tony, just a FYI:

The first time I tried to use your (excellent) tool, I ran into a client
who didn't allow binaries (.exe's) on their servers. In fact they had a
program that would periodically go through and "scrub" them away. Took
awhile to realize that's why the updater files needed frequent replacing.
:-)

Ended up rolling my own variation based on ideas gathered from the links
from your site. Final product uses only .mdb/.mde's, which doesn't seem to
bother the client's bots, at least so far...
 
George Nicholson said:
The first time I tried to use your (excellent) tool, I ran into a client
who didn't allow binaries (.exe's) on their servers. In fact they had a
program that would periodically go through and "scrub" them away. Took
awhile to realize that's why the updater files needed frequent replacing.
:-)
Click to expand...

<chuckle> Oh well. Not much I can do about that.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
George Nicholson said:
The first time I tried to use your (excellent) tool, I ran into a client
who didn't allow binaries (.exe's) on their servers. In fact they had a
program that would periodically go through and "scrub" them away. Took
awhile to realize that's why the updater files needed frequent replacing.
:-)
Click to expand...

BTW what improvements would you like to see?
Ended up rolling my own variation based on ideas gathered from the links
from your site. Final product uses only .mdb/.mde's, which doesn't seem to
bother the client's bots, at least so far...
Click to expand...

Just wait. Sooner or later the bots will realize that not only can
MDBs contain code so can .docs and .xlss and they'll be deleted.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Just wait. Sooner or later the bots will realize that not only can
MDBs contain code so can .docs and .xlss and they'll be deleted.
Click to expand...

Yep, and then they'll have these really, really big servers and nothing
'legal' that they can store on them :-)
 
I have managed the versions with a text file: cms_verN.N.inf
a shortcut in the desktop calls the batch on the server, this batch
call the mde in the users pc
when the frontend updates in the server , change the .inf name with
the version (ie cms_ver2.1.inf)
CMS is the acronym of my app, useful if I am going to distribute more
than one app.

@echo off
set cms-path=[network path]
cd %cms-path%
for %%i in (cms*.inf) do set cms-ver=%%i
if exist %userprofile%\%cms-ver% goto begin

:update
if exist %userprofile%\cms*.inf del /q %userprofile%\cms*.inf >null
copy /v/y "%cms-path%\shell-cms.bmp" "%userprofile%\*.*" >null
copy /v/y "%cms-path%\shell-cms.mde" "%userprofile%\*.*" >null
copy /v/y "%cms-path%\cms*.inf" "%userprofile%\*.*" >null

:begin
cd %userprofile%
start shell-cms.mde

:end
exit
 
Back
Top