Difference between revisions of "Issues:MatchUp Object"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
See [[MatchUp Object:Best Practices|MatchUp Object Best Practices]] for override instructions. | See [[MatchUp Object:Best Practices|MatchUp Object Best Practices]] for override instructions. | ||
Line 25: | Line 14: | ||
Revision as of 15:01, 2 July 2014
Large KeyFile Size effect on Memory resources
By default, MatchUp object allocates a large SetUserInfo, the unique identifier attached to built match key - 1024 bytes. See MatchUp Object Best Practices for override instructions.
Fuzzy: Legacy Matchcodes
Legacy Matchcodes, imported from previous versions, allowed a Fuzzy: Near setting of '0'. This is incompatible with the current version and can cause an error. Using the interface to edit the matchcode by changing the Distance to 1 will resolve the problem