We´ve made a script in Windows-NT to test some Office-applications and this script runs good.
Then we put the same (without any change) script on a Windows-XP-pc and run it. Now the script stops at some times (e.g the mouse don´t click on a file in a snakelist). When we touch the mouse a littje bit, the script runs further.
Is there someone who has the same problem?
That is pretty common. Look up the GUITYPE data type in help. You probably will just need to redo some parts of your window declarations with 'gui specifiers' (see window declaration help). If your tests used the windows builtin 'Save As' dialogs, then that part of the code will need to be rewritten to handle the new dialogs. Other similar dialog troubles will probably come up.
Thanks for your answer to my problem, but the redo of de declarations don´t work. The script runs fine if I touch the mouse when the script stops to run. The only way the scrips runs to the end is if I put some sleep-statements in the script, but this is not what I want. Maybe there is someone who can help me with the problem. Maybe for SilkTest there is a great difference among Windows-NT and Windows-XP.
Sleep in automation scripts is more than just normal, it is frequently required. Many people seem to believe that it is bad practice (as it can be with other types of s/w), but I think this is completely false.
I agree that frequent use of sleep statements is a good idea and is often required to get scripts to run consistently. Some other useful functions are WaitFor() (that waits for a window to exist), WaitForReady() (that waits for a window to exist and become active) and WaitGone() (waits for a window to close). Often I found our scripts would have to sleep for a long time to work on our slower machines which meant wasted sleep time on a faster machine. These functions make sure that the script doesn't sit idle for very long, which can translate into much faster scripts if they are used frequently.
ps - I think you can find code in the downloads section for WaitFor() and WaitGone()