Hi RedFox, I have looked at your question several times, since you asked it 3 days a go. Waiting for somebody else to answer it, because I personally did not understand it. But since nobody else seems to have an answer either, then let me try to help you. What is the context of this question? What is it that you are trying to do? Your subject says you want to convert a text from unicode and NAV 2018 TO anse and NAV 2009. Are you trying to downgrade a NAV 2018 installation?? And what is this about a barcode and a string in NAV 2018 and 2009? Where do you get this string from and how did you get it into NAV? Here it sounds like your question is about upgrading code that worked in NAV 2009 but not in NAV 2018? As you described the way text encoding has changed quite a lot from NAV 2009 to 2018 (I don't remember any major changes since BC, except that the SaaS may be more restrictive). There are a few factors in play here. We have to consider both database encoding (assume your NAV 2009 is also SQL, otherwise more factors) and the way we get data in and out of NAV and which codepage is used by the client. I come from a country with three special letters ÆØÅ, which very often are messed up, unless you are really careful. We used to have to run special conversions of the data whenever importing/exporting anything. Today (NAV 2018/BC+) we either have this functionality standard in NAV as encoding options when importing/exporting, or as supporting codeunits we can use in our development. Love to help you, but please give me more to work with.
↧