{{Quickfixn}} How to prevent rejection of message missing an *optional* field.

[Manuel Lopez]

Mike,
Thanks.  The language is from the spec, but I think it has generated
questions because the meaning isn't so clear or applicable.  In my
case there was no conditional field at all (having a field whose value
when set requires the presence of another field, --which would make
for a convoluted definition file to figure out).  So I would have
expected only a "field access error" or "field not found error" or a
plain null exception error message with the field tag number -- but
it's clear now with the explanation.
-Manuel

>>FYI, the error message comes straight from the FIX specification.
>>See tag 380 for reference:
>>http://www.fixtradingcommunity.org/FIXimate/FIXimate3.0/en/FIX.5.0SP2/tag380.html

--
Mike Gatny
Connamara Systems, LLC