KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q85055: FFAPI: What to Watch for When Building an FFAPI File

Article: Q85055
Product(s): Microsoft Mail For PC Networks
Version(s): MS-DOS:3.0
Operating System(s): 
Keyword(s): 
Last Modified: 15-NOV-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Mail Software Development Kit: FFAPI for Gateways and Applications, version 3.0 
-------------------------------------------------------------------------------

SUMMARY
=======

The most common problem encountered when building a File Format Application
Programming Interface (FFAPI) file is specifying the wrong line termination
character. This is usually identified by error 144, "Unable to partition line
%s".

FFAPI looks for a carriage return (<CR>) by default. If the line
termination character used in the file is <CR><LF> or just
<LF>, FFAPI will have problems parsing the line.

To ensure that FFAPI will parse the file correctly, make sure FFAPI knows what
line termination character is being used. To specify this, use the -F parameter
on the command line, according to the following format:

  Character  Parameter
  ---------  ---------

  <CR>       -F0
  <LF>       -F1
  <CR><LF>   -F2

REFERENCES
==========

"Microsoft Mail for PC Networks Software Development Kit Application File Format
API"

"Microsoft Mail for PC Networks Software Development Kit Gateway File Format
API"


Additional query words: 3.00 2.1a pcmail

======================================================================
Keywords          :  
Technology        : kbAudDeveloper kbMailSearch kbSDKSearch
Version           : MS-DOS:3.0

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.