Our apologies if our email response sometimes are less than friendly. I assure you it is out of frustration with our inabaility to sometimes give the required response than annoyance with the issue being raised in the email.

We rely on, and pay for, information from sources that we do not control, are inconsistent over time in data accuracy and scope of content and have little or untimely support when we raise issues with them. And while we acknowledge our responsibility to our subscribers, in some situations we cannot fully understand or get explanations why data does or does not appear or appears only under certain conditions, especially when those conditions change without notice or have no explanation. Believe me when I say that nothing would please us more than to have the ability to deliver comprehensive, accurate information on a consistent basis. To that end, we are constantly looking for new sources of information that we can legally access and integrate into a seemless presentation.

Many times questions or issues about EF are debated within FT forums, and that's just fine with us, good and bad. That's one way we learn. But, sometimes the details of the issue are never emailed to customer service at EF and we have no way of fully understanding the problem and either resolving it, carrying on a dialogue with the user through email to dig deeper, or at least explaining its cause properly. We appreciate JohnAx's email to us in this case, but you might be surprised how often this is not done. And, as is the case with the problem the JohnAx brought to our attention, if there is a problem we can fix we will do so as quickly as possible.

One last comment. I sometimes get PM'ed here at FT to report and troubleshoot a specific and timely problem on EF. While I do not mind PM's, I am not the person to report timely operational issues to. This will only delay our repsonse to you and the issue. Just email [email protected].

Thank you again.

EFV