Hi Bob,

The ShellExecute API #12636 should work better for you.

>I have a function which launches the default browser and accesses a URL something like this (an extract):
>
>if FindExecutable ("c:\dummy.htm", "", @lcResult)>32
> lcfile=Left (lcResult, AT(Chr(0), lcResult)-1)
> SET classlib TO Process ADDITIVE && Ed Rauh, RIP
> oProcess = CREATEOBJ('API_AppRun',lcfile+ [ "]+tcURL+["],'C:\','NOR')
> oProcess.LaunchApp()
>endif
>
>But this doesn't work for AOL users if the URL (tcURL) is something like "http://www.mapquest.com". AOL (v8 and v9) returns a message that "The file may not be supported by AOL" and it offers to open the link with a text editor instead.
>
>This method using API_AppRun only works for AOL users if the URL is an .HTM file. It doesn't work to go to a domain name (and index.htm doesn't exist in this example) and it doesn't work when the URL is a script like PHP, ASP, etc.
>
>On the other hand, this does work for AOL users, even for domain names and scripts:
>
> RUN /N &lcFile &tcURL
>
>My question is: why did I use API_AppRun <g>? I only want the window to open in normal mode and I don't want to suspend operation until it closes, kill the app window manually, etc., all of which seem to be the advantage of API_AppRun. The threads here talk about it avoiding a DOS window but I don't see it. Is that because it flashes by too quickly and a user with a slower computer will see it?
>
>I need to support users with a wide range of browsers, including AOL's. They also have a wide range of operating systems, as far back as Win95.
>
>Is there some way to get API_AppRun to work with AOL? If not, is there some disadvantage (compatibility, etc.) to using the RUN command for all users?
>
>Thanks for any help.
>
>-Bob