Subject | Re: [firebird-support] Update in clients |
---|---|
Author | Doug Chamberlin |
Post date | 2005-07-05T02:50:15Z |
At 7/4/2005 10:10 PM (Monday), Gustavo wrote:
1) Keep an area on the server shared and let a single shared copy of the
EXE reside there. As you have recognized, this is no longer necessary but
does help avoid the update problem.
2) If you REALLY want the users to run from a local EXE, create a small app
that lives alongside the main app. Have the users run the small app instead
of the main one. The small app does nothing more than compare the local
copy of the main app's exe with a master copy on a server. If the master
copy is newer, then make a local copy that replaces the older one. Then
transfer control to the local main app and exit. This is a really cheap but
effective auto update feature.
FWIW, this really is not a Firebird support question so let's not drag it
out with a prolonged discussion.
>Can anyone tell me if there is a way to avoid this?I see two choices:
1) Keep an area on the server shared and let a single shared copy of the
EXE reside there. As you have recognized, this is no longer necessary but
does help avoid the update problem.
2) If you REALLY want the users to run from a local EXE, create a small app
that lives alongside the main app. Have the users run the small app instead
of the main one. The small app does nothing more than compare the local
copy of the main app's exe with a master copy on a server. If the master
copy is newer, then make a local copy that replaces the older one. Then
transfer control to the local main app and exit. This is a really cheap but
effective auto update feature.
FWIW, this really is not a Firebird support question so let's not drag it
out with a prolonged discussion.