The only field where a line feed could be used would be the description field.  If you are trying it on any other field you should not.

That's not helpful.   How about a link to Sages functions with examples?

It's on a udf field, by the way, and it used to work when I was importing from MS Access and used chr(10) + chr(13).  But now when I import from MS Sql Server and use char(10) + char(13), the line feed/carriage return seems to get stripped out.

That's not helpful.   How about a link to Sages functions with examples?

It's on a udf field, by the way, and it used to work when I was importing from MS Access and used chr(10) + chr(13).  But now when I import from MS Sql Server and use char(10) + char(13), the line feed/carriage return seems to get stripped out.

google pvx functions and look for information on Providex.

Just to make sure, your first post was 13 (carriage return) and 10 (line feed), your last was 10 & 13, backwards.  Any chance it's that simple?  Also, are you using odbc?  If so, can you odbc to sql server vie access, then odbc to Access from Mas?

I would suggest looking at the raw data with DFDM. MAS use to use ~;~ for a carrage return and you use to be able to import that into descriptions to make like feeds and paragraph breaks.  

I've tried BigLouie"s suggestion of the ~;~ and it did not work.  It did not recognize that as a line feed.  Just showed the ~;~ in the field.  I'm on 4.5 and I looked in the file to see what the existing line feed character is in there and it looks like DF or char(223). But when I tried importing that way it did not work either.   We have formatted text (multiple line breaks) that I'd like to import to extended descriptions in CI Item extended descriptions.  Any more ideas?  

I would also like to know the resolve to this.

This was the answer for my VI import to SO lines in Sage100 Advanced 2016.  I used "chr(13) + chr(10)" and got a line break in the comment field.

Now we're moving to Sage 100 Premium 2019, and this no longer works.

v2017 Premium, ABX data (with Skip Source Data Truncation enabled):

Result:

It turns out there was a backslash \ right before the chr (13) which I guess escaped that character.  I just put a space after the backslash and the line break appeared.  Thanks for replying, or I probably wouldn't have stared at it long enough to figure this out!