Mixed results using ControlSetText

[fRequEnCy]

Hello all. I have mixed results using ControlSetText. What happens is sometimes it doesn't always work. Perhaps a timing issue?

Here is a simple example script:

$var = "C:\testfile.txt"
WinWait("Open", "")
If Not WinActive("Open", "") Then WinActivate("Open", "")
WinWaitActive("Open", "")
Sleep(500)
ControlSetText("Open", "", "Edit1", $var, 1)
ControlSend("Open", "", "Edit1", "{ENTER}")

This is an open dialog. What I want is to pass the file name to the control and then press enter so it will load that file. I get mixed results though. I didn't always use a sleep function but stated to and seems it works fine but worry about it not working on other systems as the timing may just work well for my system. Any suggestions on a better way to tackle this?

[fRequEnCy]

Where does the open dialog come from? If you are trying to open "C:\Test.txt", then these are probably the best two ways to do it.

ShellExecute("C:\Test.txt", "", "", "open") will open the file with it's default program.

Run("notepad.exe " & "C:\Test.txt") will open the file with notepad.

The Open Dialog is from various programs which is why I have mixed results. I'm not actually trying to open a txt file. Was just using as an example. So thanks for the reply but doesn't solve my problem in that case.

[fRequEnCy]

Bump. Sorry but never got a fix for this issue. It is definitely a timing issue as if I put a longer sleep then it will work. But I don't want to have to use a long sleep if I don't have to. So must I use a sleep in this case or is there a better way of coding this? I find that a sleep(500) works about 9 out of 10 times give or take. I tested many times as I'm writing a script that will be used publicly and don't want the timing to be off. Just wanting it to be perfect is all and not have the occurrence of it not sending the text to the control before I send {ENTER}.