none
SDEF RRS feed

  • Question

  • Anyone worked on the Standard Data Exchange Format (SDEF) for the US Army???  They seem to require Primavera, but I know MS-Project can do just as well....
    Monday, June 13, 2011 5:01 AM

Answers

  • File formats supported are listed here at http://office.microsoft.com/en-us/project-help/file-formats-supported-by-project-2010-HA010373155.aspx

    No, MS Project does not support SDEF.

    --Ismet

    • Proposed as answer by Ismet Kocaman Monday, June 13, 2011 2:47 PM
    • Marked as answer by WP Iverson Tuesday, June 21, 2011 9:45 PM
    Monday, June 13, 2011 5:45 AM
  • Well, I've written the specification in VBA as a macro, and it works fine.  Writes their plain text format out, and checks solid with the USACE SDEF checker software.  But that macro approach limits the distribution and user interaction to select output options, like picking custom fields to be used as USACE "features of work."  So I need to re-write this in Visual Studio and create an Add-In.  Any suggestions on what path to take down that road????
    • Marked as answer by WP Iverson Thursday, June 30, 2011 5:04 AM
    Tuesday, June 21, 2011 9:48 PM
  • I believe you may get some feedback if you post your question to Project Customization and Programming forum at http://social.msdn.microsoft.com/Forums/en-US/project2010custprog

    --Ismet

     

     


    • Marked as answer by WP Iverson Thursday, June 30, 2011 5:04 AM
    Tuesday, June 21, 2011 10:57 PM

All replies

  • File formats supported are listed here at http://office.microsoft.com/en-us/project-help/file-formats-supported-by-project-2010-HA010373155.aspx

    No, MS Project does not support SDEF.

    --Ismet

    • Proposed as answer by Ismet Kocaman Monday, June 13, 2011 2:47 PM
    • Marked as answer by WP Iverson Tuesday, June 21, 2011 9:45 PM
    Monday, June 13, 2011 5:45 AM
  • Well, I've written the specification in VBA as a macro, and it works fine.  Writes their plain text format out, and checks solid with the USACE SDEF checker software.  But that macro approach limits the distribution and user interaction to select output options, like picking custom fields to be used as USACE "features of work."  So I need to re-write this in Visual Studio and create an Add-In.  Any suggestions on what path to take down that road????
    • Marked as answer by WP Iverson Thursday, June 30, 2011 5:04 AM
    Tuesday, June 21, 2011 9:48 PM
  • I believe you may get some feedback if you post your question to Project Customization and Programming forum at http://social.msdn.microsoft.com/Forums/en-US/project2010custprog

    --Ismet

     

     


    • Marked as answer by WP Iverson Thursday, June 30, 2011 5:04 AM
    Tuesday, June 21, 2011 10:57 PM