I don't know much about the shellexecute call but I think the workaround is a better solution anyway. One reason why ShellExecute may not have been working for you is that .txt files on your machine don't have any associated program. What about the case where a user has a machine that has .txt files associated with a program other than notepad? I'm sure it would be rare but it could happen. I know on my machine .txt files are associated with a text editor called ultraedit. So if you really wanted to pop up notepad the run command is the best way IMO.



>Works fine Rip. Still bugs me that ShellExecute won't work but this is a fine workaround. Thanks.
>
>>How about using the run command instead?
>>
>>run /N notepad "d:\VFPAPPS\APPDOCS\PROCS.TXT"