![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
The accented y is character 253 from the ASCII Latin 1 character set so this is what I would expect. Are you sure that you need value marks? Most packages I have come across use field marks for the line separator in which case you need char(254). Martin Phillips, Ladybridge Systems. |
#4
| |||
| |||
|
|
No charater 253 is the value mark, but I did try 254 just for prosperties sake and I got another strange character On Jan 26, 10:27 am, "Martin Phillips" <MartinPhill... (AT) ladybridge (DOT) com wrote: The accented y is character 253 from the ASCII Latin 1 character set so this is what I would expect. Are you sure that you need value marks? Most packages I have come across use field marks for the line separator in which case you need char(254). Martin Phillips, Ladybridge Systems. |
#5
| |||
| |||
|
|
I am sending an email using outlook at most sites all I have to do is put a char(253) in the text of the email for a line seperator, BUT on one site when I do that I get a 'Y' character with 2 dots over the top. can anyone help |
#6
| |||
| |||
|
|
In Linux the separator is char(10) (line feed). Have you tried that? |
#7
| |||
| |||
|
|
"Jeffrey Kaufman" wrote: In Linux the separator is char(10) (line feed). Have you tried that?CRLF would be used for Outlook: CHAR(13):CHAR(10) Example of MV/Outlook integration here: removeNebula-RnD.com/blog/general/2006/11/outlookappt1.html remove the remove T |
#8
| |||
| |||
|
|
I tried 13 and 10, it must be something inside of VIA that is throwing it off. Tony wrote: CRLF would be used for Outlook: CHAR(13):CHAR(10) |
#9
| |||
| |||
|
|
spayne wrote: I tried 13 and 10, it must be something inside of VIA that is throwing it off. Tony wrote: CRLF would be used for Outlook: CHAR(13):CHAR(10)Via Duct? Via Systems? Univision? Web Wizard? Can you give us an idea of what tools you're using and how you're using them? Unless you're doing HTML emails, setting CRLF to separate lines in your email is your goal. It's possible that some communications product would translate CRLF into something as directed by an Option setting. I doubt this is the case. Before the transmission, did you do something like this?: BODY = SWAP(BODY,@VM,CHAR(13):CHAR(10)) Also, for MANY reasons that have been cited in Outlook related forums and Microsoft KnowledgeBase articles, you need to be VERY careful about using Outlook as a server rather than as a user interface for a user sitting at the PC. I've been doing this sort of thing for years and for some projects I'm hesitent to interface to Outlook unless I'm sure I understand the client's environment - and that the client understands the considerations of the technology. If you aren't aware of these issues, you will find your application just stops without warning, perhaps locking up both the PC running Outlook and the DBMS port attempting the interface. Good luck, TG@ cautionadvisedNebula-RnD.com |
#10
| |||
| |||
|
|
Via Duct. I have 5 other sites and it works fine. On Jan 27, 4:32 pm, Tony Gravagno g6q3x9lu53... (AT) sneakemail (DOT) com.invalid> wrote: spayne wrote: I tried 13 and 10, it must be something inside of VIA that is throwing it off. Tony wrote: CRLF would be used for Outlook: CHAR(13):CHAR(10)Via Duct? Via Systems? Univision? Web Wizard? Can you give us an idea of what tools you're using and how you're using them? Unless you're doing HTML emails, setting CRLF to separate lines in your email is your goal. It's possible that some communications product would translate CRLF into something as directed by an Option setting. I doubt this is the case. Before the transmission, did you do something like this?: BODY = SWAP(BODY,@VM,CHAR(13):CHAR(10)) Also, for MANY reasons that have been cited in Outlook related forums and Microsoft KnowledgeBase articles, you need to be VERY careful about using Outlook as a server rather than as a user interface for a user sitting at the PC. I've been doing this sort of thing for years and for some projects I'm hesitent to interface to Outlook unless I'm sure I understand the client's environment - and that the client understands the considerations of the technology. If you aren't aware of these issues, you will find your application just stops without warning, perhaps locking up both the PC running Outlook and the DBMS port attempting the interface. Good luck, TG@ cautionadvisedNebula-RnD.com- Hide quoted text -- Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |