Re: [Quickfix-developers] "Invalid tag number" error for proprietary field

[Alvin W. <AW...@FF...>]

This will be a lot easier! Sometimes, it is hard to maintain counterparts'=
=20
proprietary fields since we do not need all of them. And if 2 counterparts=
=20
use the same field by coincidence, I have to create 2 XML files.=20






Joerg Thoennes <Joe...@ma...>
02/16/2005 10:14 AM

=20
        To:     Yihu Fang <Yih...@re...>
        cc:     dav...@ma..., Alvin Wang <AW...@FF...>,=20
qui...@li...
        bcc:=20
        Subject:        Re: [Quickfix-developers] "Invalid tag number" erro=
r for proprietary field


> If you always want to pass through user defined fields without using
> data dictionary for validation, change the line 154 of
> DataDictionary.cpp of QuickFIX 1.9.4 as following
>=20
> 154c154
> <     if ( m_beginString.getValue().length() && field.getField() <
> FIELD::UserMin)

Instead of changing the code this could get a configuration option, e.g.

                 ValidateUserDefinedFields=3DY (default)
                 ValidateUserDefinedMessages=3DY (default)

I wonder what Oren thinks about this.

Cheers, J=F6rg

--=20
Joerg Thoennes
                                http://macd.com
Tel.: +49 (0)241 44597-24      Macdonald Associates GmbH
Fax : +49 (0)241 44597-10      Lothringer Str. 52, D-52070 Aachen



**********************************************************************
This e-mail message is intended solely for the use of the addressee. The me=
ssage
 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 immediatel=
y by
return e-mail (including the original message with your reply) and then del=
ete
and discard all copies of the message.
We have taken precautions to minimize the risk of transmitting software vir=
uses
 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 d=
amage
 caused by software viruses.
**********************************************************************