I would like, if possible, to implement an automatic update check from the software to our web site.

At the users request, I would like to:

- get OI to have a look at a specific file on our web site

- return the contents so I can compare to the current app release

then if appropriate

- download a zip file (or folder) from the web site which has a RDK module

- install the relevant RDK (which I already do)

Any ideas on how this can be acheived.

My aim is to try and replicate the MS service pack updates or virus checking updates, so that the users are always running on the latest versions.

Thanks

Colin

I have tried the ShellExecute to an EXE file on the web site, so I can now download the actually RDK install files.

What I still need to know is how to check for a files existence and return its contents, eg a version number in line 1 of a TXT file.

=== At 06 MAY 2005 10:14AM support@sprezzatura.com wrote: ===

Use the FTP socket routines in OI. Always have a "Latest release" file on the site. Read this and compare to version….

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

Colin,

Sprezz's suggestion is a good one. A few of our client's systems are already doing exactly that. You can also use remote engine communication to do this. This approach doesn't require you to upgrade OI to 7.1 and you can do direct updating of system tables without needing to write the RDK to a folder first.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

I gave a second presentation dealing with ftp_manager .. an open source product i have .. basically wraps the ftp functions around.

if you are interested let me know ..

dsig _at_ sigafoos.org.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

If you are using the Universal driver you can create a rev param file on your client machines which points to a share on your web server.

client side revparam is in \oi71\upgrades,

looks like

serveronly=1

servername=www.myhost.com

port=8085

sharename=myapp

server side config file has a share for each application ( or even each subscriber )

your app can then attach_table('UPGRADES', , ), use a timestamp comparison of some sort as suggested earlier in this thread, run an rdkinstall if needed. You could even put installation confirmations back to the server. Using subscriber specific shares you could disable updates when subscriptions expire or build updates specific to the modules they have purchased.

View this thread on the Works forum...