ShellExecute

[GEOSoft]

This is only an observation and not a feature request!!!!

It's probably way too late anyway.

I thimk that ShelExecute and ShellExecuteWait should have been made moe compatible with Run and Run Wait. That is It should be

ShellExecute(<Path/file>,[working dir],[showflag],[Parameters],[verb]) with Open being the default Verb.

I didn't notice the difference until I went to change a dozen or so Runs to Shell Executes

All of the lines involved Used Run(<File>,'',@SW_MAXIMIZED) and it would have been great if I could have changed Run to ShellExecute and that was all.

Instead I had to change it to

ShellExecute(<File>,'','','Open', @SW_Maximized)

Not a mind boggling situation, howerver it didn't seem as user friendly as it could have been.

[Valuater]

I didn't notice the difference until I went to change a dozen or so Runs to Shell Executes

Just click the button

8)

[GEOSoft]

Just click the button

8)

Wise Guy!! 8)

Thats how I did it (I said it wasn't mind boggling) but actually the method you posted won't work exactly as posted.

Some of the files were CHM's others were HLP's so there wre 2 different apps involved.

I used Global Search and Replace (Nice App!! ) to do it. It allows regular expressions in the string so it would replace the

Run ("hh.exe "<filename>

With ShellExecute (<Filename>

and switch the rest of the string.

[Jon]

The parameters are different because the underlying Run API has the command.exe AND command line parameters passed as a single parameter whereas the underlying ShellExecute API separates the command.exe and the parameters. Any code that I wrote to try and convert one to the other would no doubt be flawed - so I didn't.

[GEOSoft]

The parameters are different because the underlying Run API has the command.exe AND command line parameters passed as a single parameter whereas the underlying ShellExecute API separates the command.exe and the parameters. Any code that I wrote to try and convert one to the other would no doubt be flawed - so I didn't.

Thanks for that explanation Jon

I didn't want you to re-write code, it was just an obsevation. I think I'll probably just write a function to change it in the future because I have several older scripts (before we had shellexecute) that should be changed. I already have a script that updates syntax tha is obsolete to the new syntax. As in TimerStart = Timer Init and TimerStop = TimerDiff. I'll just add the function into that script as an option.

BTW I was in the middle of preparing a PM for you on another matter. so you can expect it soon.