Of note, this issue is addressed since TreeAge Pro 2012 has been released. Please look at their policies for an upgrade.
