The person here working on this is out sick today. I'll see what I can find out from others. I may not have an answer till that person gets back to the office tomorrow.
The engineers that would be working on correcting this have been tied up in a big release. They expect to resume work on this fix next week.
Regards,
Jay F.
Product Manager
_____________________________________
Have a suggestion to improve our products?
Click Support --> Request a Feature in eSignal 11
My apologies for the lack of a solution thus far. I'm checking with the manager of group responsible for this fix, and will update this thread as soon as I hear more information.
In the meantime, I will be moving this thread over to Data Inquiries forum as it is more applicable there.
Regards,
Jay F.
Product Manager
_____________________________________
Have a suggestion to improve our products?
Click Support --> Request a Feature in eSignal 11
Still hunting this down... thanks for your patience.
Regards,
Jay F.
Product Manager
_____________________________________
Have a suggestion to improve our products?
Click Support --> Request a Feature in eSignal 11
Here's a summary of the issue. We have found the cause of this SIMEX problem, however it unfortunately requires a large amount of man-hours to correct. This is on the list of items to address, but there is no estimate for when this will be fixed. My guess it will be greater than 3-6 months before we see any movement on this.
Sincerely,
Jay F.
eSignal Community Support
Regards,
Jay F.
Product Manager
_____________________________________
Have a suggestion to improve our products?
Click Support --> Request a Feature in eSignal 11
Comment