[Quickfix-developers] Re: "Value is incorrect (out of range) for this tag" error for proprietary field value

[Oren M. <or...@qu...>]

Well, if you are ok with any value coming in, you can just delete all =
the enumeration elements from the field.  Basically it sounds like you =
want the field to be free form, in which case it makes no sense to have =
any enumeration elements to begin with.  Although I'm not really sure =
what your application would have done with the UTF_8 value if it didn't =
know to expect it beforehand. =20

--oren
  ----- Original Message -----=20
  From: Alvin Wang=20
  To: qui...@li... ; =
qui...@li...=20
  Cc: dav...@ma... ; Joerg Thoennes ; Oren Miller ; Yihu Fang=20
  Sent: Tuesday, June 07, 2005 5:03 PM
  Subject: "Value is incorrect (out of range) for this tag" error for =
proprietary field value



  Hi,=20

  Can we have a new configuration that allows proprietary field value =
for a tag.  For example, today we received a message with =
MessageEncoding(347)=3DUTF-8. However, in Quickfix dictionary, it is =
UTF_8 (BTW, i believe UTF-8 is official according to FIX document). We =
had to manually edit FIX44.xml and restart our FIX engine. That means, =
each time counterparty has a proprietary field value, we have to =
manually add it into the dictionary, otherwise the message will be =
rejected by QF.=20

  Thanks=20
  Alvin=20
  ********************************************************************** =
This e-mail message is intended solely for the use of the addressee. The =
message may contain information that is privileged and confidential. =
Disclosure to anyone other than the intended recipient is prohibited. If =
you are not the intended recipient, please do not disseminate, =
distribute or copy this communication, by e-mail or otherwise. Instead, =
please notify us immediately by return e-mail (including the original =
message with your reply) and then delete and discard all copies of the =
message. We have taken precautions to minimize the risk of transmitting =
software viruses but nevertheless advise you to carry out your own virus =
checks on any attachment to this message. We accept no liability for any =
loss or damage caused by software viruses. =
**********************************************************************