Try TDtesteng idea first if that doesn't work try adding a wait(x) statement. Where is is the number of seconds to wait before going to the next instruction. I have found that 3-5 seconds usually works best.
I figure if you have the courage to get out of bed in the morning, then how bad can the day be.
Also, I've found that when recording, WR likes to create the following command sequence (at least in WR 6.02):
set_window("Some Window", 20);</pre>
I find it helpful to edit the script to reverse the sequence of these two lines, so that the set_window(), with its wait time parameter, runs first. Otherwise, the win_activate() function will raise an error if the window isn't there yet.
Software Testing (n): 1. The art of trying to increase your confidence in a piece of software by finding everything that is wrong with it.