R
Roberta Miller
Guest
Lieven, I went back to your original case and tested the reproducible. The problem still occurs even in OpenEdge 11.5 (Infragistics UltraControls 14.2), so it really is a catch-22. In your repro, ForceNativeMessageFilter corrects the issue and does not cause any other visible problems. Other applications might not be so lucky, because the AVM makes a call that Infragistics documents as incompatible with ForceNativeMessageFilter (see Matt's comment above). Fortunately, the customer in the new case found that the problem he had used ForceNativeMessageFilter to correct no longer occurred in his current OpenEdge version (11.3). We haven't yet heard from anyone who has both a problem that ForceNativeMessageFilter corrects and a problem caused by using ForceNativeMessageFilter, but that could conceivably occur. Anyone in that situation should contact Technical Support so we can look for a solution that does not require ForceNativeMessageFilter. In the meantime, I will remove article 000033230 from the public knowledge base because we can no longer recommend that solution, and add a note to article 000058698 for readers to contact Technical Support if they are currently using ForceNativeMessageFilter to correct a specific problem. Thanks for pointing out the conflict between the two articles.
Continue reading...
Continue reading...