At 09:24 AM 1/21/2003 +1000, Edwards Lucas wrote:

Now that we've upgraded to v6.5++ 1.862xRT03 the problem has magically disappeared.
Might pay you to do the same.
Enjoy the benefits of staying CURRENT!

Very Best Regards,

Razzak.

Reply via email to