In currently supported versions of Sage 100, because of a limitation in addressing that does not allow data files to be larger than about 2 GB in size, the program automatically create one or more additional segmented files when the number of rows/records in a table take up more than 2 GB of space.
If a segmented file takes up to 2 GB of space, another segmented file is created and used, and so on.
- Example:
- IM_ItemTransactionHistory.M4T
- IM_ItemTransactionHistory.M4T.001
- 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: There IS a limit to the number of segments! The maximum is 16, including the original *.M4T file. Around this number, you may encounter an Error #16 or other errors 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?
|