> This has been fixed in 3.0 Final! Sorry.. I should have also said.. We are looking for a RC3 or Final release either end of this week or early next week! This behavior has definitely been fixed! Cheers Alan Runyan