02-12-2007 05:12 PM
02-13-2007 05:37 PM
Hello,
I have opened a dialog with R&D to determine if this is a problem in documentation, a problem with behavior, or there is a rational explanation for the behavior. At this point, it appears as though behavior contradicts documentation. If it turns out to be a legitimate bug, we'll repost with the formal corrective action request ID (CAR ID).
For now, a workaround will be to set the refresh rate in seconds to something very large, effectively causing it not to refresh the device.
Best Regards,
JLS