BUG: MIFST <SPNAME> Tag Placed in Wrong Position

ID: Q199154

The information in this article applies to:

Microsoft Internet Finance Server Toolkit, versions 1.0, 1.01

SYMPTOMS

In the Microsoft Internet Finance Server Toolkit (MIFST) SDK, the sample OFX_FI_Frame component has a bug that places the <SPNAME> tag in the wrong position within a <MSGSETCORE> aggregate.

CAUSE

The initial public specification for OFX 1.02 had the location of the <SPNAME> tag for the <MSGSETCORE> aggregate as the optional second attribute. This is where the sample OFX_FI_Frame component places the <SPNAME> tag. The addendum to the OFX 1.02 specification indicates that the tag should actually be the last tag for the <MSGSETCORE> aggregate. Therefore, the tag should have been moved in the code sample OFX_FI_Frame component.

RESOLUTION

In order to change the location of the <SPNAME> tag in the sample OFX_FI_Frame component, you can make a simple change to the AddResponse method of the CAG_MessageSetCore class (found in aggregate.hpp). The following declaration fixes the problem:



   HRESULT Add_Response( CFI_Frame *pFrame )
   {
      ADD_CHILD("MSGSETCORE");
      ADD_ENTITY("VER", m_csVer);
      ADD_ENTITY("URL", m_csURL);
      m_cOFXSecurity.Add_Response(pFrame);
      ADD_ENTITY("TRANSPSEC", m_csTranspSecurity);
      ADD_ENTITY("SIGNONREALM", m_csSignOnRealm);
      ADD_ENTITY("LANGUAGE", m_csLanguage);
      ADD_ENTITY("SYNCMODE", m_csSyncMode);
      ADD_ENTITY("RESPFILEER", m_csRespFileError);
      IF_ADD_ENTITY("SPNAME", m_csSPName);
      LEAVE_CHILD();
      return S_OK;
   }

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

The sample testbank site does not use the <SPNAME> field thus it does not encounter the problem.

Additional query words: kbDSupport


Keywords          : 
Version           : WINDOWS:1.0,1.01
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: March 31, 1999