In currently supported versions of Sage 100, there’s a limitation in addressing preventing data files to be larger than about 2 GB in size.  The program automatically creates one or more additional segmented files, when the number of rows/records in a table grows beyond this limitation.

If a segmented file takes up to 2 GB of space, another segmented file is created and used, and this process repeats as the file continues to grow.

• Example:
  1. IM_ItemTransactionHistory.M4T
  2. IM_ItemTransactionHistory.M4T.001
  3. IM_ItemTransactionHistory.M4T.002, etc.
• Example:
  • GL_DetailPosting.M4T
  • GL_DetailPosting.M4T.001
  • GL_DetailPosting.M4T.002
  • GL_DetailPosting.M4T.003, etc.

Note: When rebuilding key files files, all segmented files must be in sync and present to be properly rebuilt.

Note: The maximum number of segments is 16. This includes the original *.M4T file. Around this number,  Error #16 or other errors present when attempting to migrate or convert data, or when attempting to work with data (posting a journal or registry update, etc.).

DocLink: Error: "12 SY_RebuildFile_Bus.pvc 499" when running the Rebuild Key Files utility
DocLink: What files may be deleted or removed from Sage 100 to conserve hard disk space or to reduce backup storage volumes?