Sage 100 BoI corrupt records with extended ascii

We're currently on Sage 100 2014 (Non SQL) and we're currently running into the issues where we are being sent names containing certain ranges of extended ascii characters.

For now, we are going to limit ourselves to the first 127 in the ascii table, some of the characters from the extended ascii DO work, notably umlauts and the eszett.

Usually, if you would enter non-sage-valid characters, it would get replaced with a ?. We seem to be running into issues where two ranges of extended ascii cause sales order records to "corrupt". It seems if you use any of the extended ascii between DEC 129-142 and 147-160, the record shifts the data fields around and you get things like: The name gets shifted into the Ship code, the warehouse code gets pushed into the zipcode, etc. Is this a known issue?