Gaylen,

Are you users running application from the network or from a local drive?

>Since I don't have a network to simulate real life, does anyone see a problem with this approach to update an applicaton.
>
>Currently have a small splash screen executable to launch my program at each workstation. It has a timer and merely sets the default path and call the app. Works fine.
>
>As the number of users has grown and the increased need for changes to the program, it has becomes problematic to get all out of the program to switch out the app.
>
>I am considering using an ini file would have "do xxxx.app" in it and I will merely rename the application each time and then change the ini file to point to the newly named application.
>
>Using Execscript function I will launch the program.
>
>

>set default to H:\directory\folder
>EXECSCRIPT(FILETOSTR("xxxx.ini"))
>

>
>It seems too simple. Anyone see any downsides to this. I know there is a laucher but this seems a lot complicated unless there are problems.
>
>Thanks in advance for any responses.
>
>Gaylen