I still can’t reproduce the issue with the .NET 1.1 component. However, the latest version is 3.2.7205.0. I suggest you try it, to see if this resolves the issue. If not, we will need a sample application that reproduces the problem. so we can investigate it further. Send it to <a href=”mailto:firstname.lastname@example.org”>support</a>.
Imported from legacy forums. Posted by André (had 269 views)