Re: ON LOGON

Ok Billy.

thanks for your input. I'll investigate in that way.

Regards.

Michel.

"Billy Verreynne" <vslabs_at_onwe.co.za> a écrit dans le message news: b5cfc8$lks$1_at_ctb-nnrp2.saix.net...
> Michel D wrote:
>
> > My idea is, when a session is created by a client program, to use this
> > trigger to compare current version of the program against last release
on
> > the server, and if the server version is more recent, to copy the latest
> > exe to the client.
> > The problem is that the ON LOGON trigger is executing on the server
side,
> > so I cannot access to client files tree structure.
>
> Why not use SMS or something similar? Re-inventing the wheel like this,
> often just buys you more maintenance and development headaches that what
> the feature is worth.
>
> The simplest of methods would be to provide a check in the client software
> that does a "SELECT version_number FROM foobar WHERE application_name =
> :NAME" and then compare that with the local application version.
>
> If different, then pop up a message telling the user to upgrade. Give him
> that responsibility instead of trying to carry it for him and then sitting
> with problems your app should not have and does not need.
>
> Or use the old WinEXEC() api call (easier than the CreateProcess() ;-),
and
> call the local browser, with a URL for downloading and installing the
> latest version. Doing this via the web is also many times easier to
deploy,
> maintain and improve IMO.
>
> > Do you have an idea on what technique I could use to achive my goal ?
>
> Well, if you absolutely insists on going the Oracle route, you will buy
> yourself a heap of trouble from the start. The app will not be able to
> ovewrite many of its files (i.e. the EXE or any DLLs or OCXs) as these
> files will be locked by Windows as they are in use.
>
> This means that you will need to copy the contents down via BFILES (the
> standard package works great for this type of thing) and the app needs to
> write it to a staging area.. and then create a script that does the actual
> installation. The app then calls the script and immediately terminates to
> unlock the files for the upgrade... very messy IMO.
>
> --
> Billy
Received on Thu Mar 20 2003 - 09:10:02 CST