Sage 100

I am trying to write a VI job where I take 5 Temp fields add them together and import into a customer memo. I want the 5 temp fields to be separated by a carriage return. So the memo looks like this: Temp1 Temp2 Temp3 Temp4 Temp5 I know how to import carriage returns from a csv but not how to insert them into the VI calculation. I tried to Temp1 + chr(13) + chr(10) + temp2.. etc but then that leaves me with those weirdo characters in the file. Can anyone help on syntax for the calculation field?

Search on CHR and you'll find a recent tread discussing this. @ShawnSlavin was the one working through that thread

No, she's talking about putting them IN, not reading them. @NicoleRonchetti - I was able to do that with a client's Memo field using just what you are doing. What weirdo characters are you seeing?

That's what I get for going on memory.

They're the ones that look like a pipe character but aren't- see attached.

Is that only happening if the temp2, temp 3 etc are blank? what if you add a conditional field in there to say if temp2<>"""" does that make the character go away? Or you could try creating another temp filed that for the chr(13) + chr(10) and put that between them instead of adding them to the caluclation?

If you DFDM the file, what does it show in there?

Its showing bad characters like the ""B"" and in the edit screen squares.

Dude instead of CHR(13) + CHR(10) try CHR(223) in your import

Dude? I hope that was auto-correct, lol?

@MichelleBennion it happens regardless. Tried conditions, and it also happens wether or not the temp fields are blank.

@RobertWood I was trying to find a way to import them but ended up just separating the lines with pipes. The client didn't care enough to pursue. Looking forward to a solution for future reference though.

@AlnoorCassim Smarty pants.

@NicoleRonchetti - Did that work or are you saying he should have called you dudette???

@BrettLyder nope that wasn't auto correct dude :)

http://infosource.sagesoftwareonline.com/infasp/kdb.asp?isresolutionconceptid=534682

https://www.evernote.com/shard/s270/sh/96d9d3cf-a665-4b80-be2e-aa073809f817/2d255a0d4527a31acca0d7618fa95113

@JeffSchwenk still need to test.

@AlnoorCassim Dude- CHR(223) didn't work for me but here is the formula that I ended up using that worked. Temp001$ + $0d$ + Temp002$ + $0d$ + Temp3$ @ShawnSlavin I am adding an article to the Evernote KB which may help you for future reference.

Hmm when I manually pressed the Enter key several times in Customer Memo Maintenance with DFDM I saw it was stored with the character. From SYZCON I read that it in as Ascii 223 (hex DF). Oh well whatever I'm glad it worked out for you!

So you really just needed the chr(13) then?

Aparently. But it didn't like the dec value only the hex. Not sure why one worked and not the other but sometimes its better to not ask why. BTW in DFDM they still show the same way with the character .

Note to Self: Upon further research I've learned DFDM displays on the screen the character (that is $DF$ / CHR(223) ) as a way of representing $0D$ / CHR(13). Very simply you can't actually display a carriage return on the screen so you have to choose a symbol. It turns out the Framework convention for any memo or extended description table is to always show the but store as a $0D$ (and no $0A$ / CHR(10) line feed after either). Now I can sleep.

The student teaches the master???