Re: Programs
From: George Shubin (dx_at_dxonline.com)
Date: 07/28/04
- Next message: Dan Freeman: "Re: Inkey()???"
- Previous message: Emily: "Inkey()???"
- In reply to: Cowboy: "Programs"
- Next in thread: Tim Witort: "Re: Programs"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Jul 2004 16:32:26 -0700
If your clients have access to the Internet then see the following for
automatic program updating:
See www.dxloader.com for a program that I use to provide my clients with
transparent updates to the programs I've written for them. The way I have
it set up is this: I have an area defined on my web server for each of my
clients. I upload to that area any program or other files that I've changed
or improved. dXLoader on my client's server periodically polls that area on
my web server. If a newer file is found than one currently present on the
server, it is downloaded. dXLoader on my client's users workstation polls
their server as necessary and when it finds newer files, updates the
workstation's files. It works really slick, and has saved me tons of
long-distance charges and on-site time.
GS
"Cowboy" <Cowboy@discussions.microsoft.com> wrote in message
news:6EB8039D-9838-4E2F-B98E-EFA29F358E75@microsoft.com...
> I have developed a POS application that contains a hundred or so
individual forms which are all called from the menu and compiled into one
exe. When a change is made, I have to issue a new exe. Is there any sense
in dividing my application into the hundred or so exe's so that updates
would be smaller for issuing? This then would present a problem of managing
updates. Rather that one file, each user location would have to be
responsible for multiple updates over time, etc.
>
> Any advice will be appreciated.
> TIA
- Next message: Dan Freeman: "Re: Inkey()???"
- Previous message: Emily: "Inkey()???"
- In reply to: Cowboy: "Programs"
- Next in thread: Tim Witort: "Re: Programs"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
