That IS an odd problem. Normally, WaitNNN should work fine.
A possible solution (pending seeing what you post as your example as requested by Tanya), is that the problem may not be in the object that is the target of the WaitNNN method but the parent object itself.
For example, check out the following code snippet
function Test()
{
var Form1
var Object1
Form1 = Aliases.MyForm
Object1 = Form1.WaitAliasChild("MyObject", 2000)
//run some sort of test
Object1 = Form1.WaitAliasChild("MyObject", 2000)
}
If the Form1 takes a while to be found or is destroyed and recreated at the "run some sort of test" segment, it is possible that the second WaitAliasChild call will fail... not because Object1 is not found but because the underlying object had not resolved yet.
Again, this is just conjecture but it is an example of where I've run into similar problems.
