Hi

That was an operator error, it shouldn't happen again.


Best regards,

Gary


  ----- Original Message ----- 
  From: Phillip 
  To: [email protected] 
  Sent: Saturday, December 16, 2006 3:14 PM
  Subject: [quotes-plus] Re: The QP database has a HUGE error!!!


  Thanks Gary,

  I did download the next day and found the error corrected. 

  I am curious to know what caused the error, if this error has ever 
  happened in the past (I personally have never seen it as a daily QP 
  user for over 4 years), and what are the chances of this error ever 
  happening again in the future.

  The reason I ask is this error caused all our trading software to go 
  haywire for a day. We were unable to trade. As a systems developer 
  for a hedgefund with over 100 clients I need to know if there is any 
  chance something like this will happen in the future so I can code 
  ahead some emergency procedures for such an event.

  Phillip

  --- In [email protected], "gary" <[EMAIL PROTECTED]> wrote:
  >
  > That has been corrected already, just download again.
  > 
  > Best regards,
  > 
  > Gary
  > 
  > 
  > ----- Original Message ----- 
  > From: Phillip 
  > To: [email protected] 
  > Sent: Thursday, December 14, 2006 4:19 PM
  > Subject: [quotes-plus] The QP database has a HUGE error!!!
  > 
  > 
  > I just downloaded/updated my QP database (around 12noon PST on 
  12/14) 
  > and it appears that the data for 12/13 has been duplicated and 
  copied 
  > forward for 12/14 (in other words, QP has data for 12/14 that 
  appears 
  > to be identical to 12/13 on all securities). Furthermore, there 
  > shouldn't be any data at all for 12/14 as today has not finished 
  yet 
  > and the database isn't normally updated until around 3pm PST... 
  > 
  > Anyone else see this problem? The error is showing up in both QP 
  and 
  > Excel.
  > 
  > This is a huge problem.. it has caused all my systems to go 
  haywire...
  > 
  > 
  > 
  > 
  > 
  > [Non-text portions of this message have been removed]
  >



   

[Non-text portions of this message have been removed]

Reply via email to