Oracle SQL> SSRS output > MS-Word envelop formatting issue
We are trying to providing MS-Word's Mail-Envelope facility to end users.
Address is being fetched from oracle database as below:
AddressLine1 || chr(10) || chr(13) ||
AddressLine2 || chr(10) || chr(13) ||
CityAndZip || chr(10) || chr(13) as Address
Then in SSRS report output is showing like this, which is expected:
1234 SomeRoad
SomeOther Address
SomeCity 12345
When this SSRS report is exported into Word file, the output still looks the same. However if you look closely you will see at the end of line we have 'line feed' and 'carriage return character'. With data if you tried to use Mail-Envelop facility then the address doesn't comes into address box automatically.
1234 SomeRoad↵
SomeOther Address↵
SomeCity 12345↵
If we change these 'return characters' into paragraph Symbols manually. By going at the end of each line and press delete(the next line comes up) and then press enter(the addressline goes to line below again). This will remove the return character(↵) to paragraph character (¶). Then if you go to mail-Envelope option then address will be populated properly.
1234 SomeRoad¶
SomeOther Address¶
SomeCity 12345¶
Approaches we have tried:
- Used variations with chr(10) and chr(13), every time the problem comes to same formatting.
- Tried to insert paragraph character directly from SQL by using chr(0182). This inserts paragraph symbol but it is treated as special character(Comes as it is) and not the actual paragraph symbol from the word.
Please suggest if there is other way to resolve this problem. Or if there is better approach to satisfy the requirement itself.
Thanks.
reporting-services ms-word oracle-sqldeveloper envelope
add a comment |
We are trying to providing MS-Word's Mail-Envelope facility to end users.
Address is being fetched from oracle database as below:
AddressLine1 || chr(10) || chr(13) ||
AddressLine2 || chr(10) || chr(13) ||
CityAndZip || chr(10) || chr(13) as Address
Then in SSRS report output is showing like this, which is expected:
1234 SomeRoad
SomeOther Address
SomeCity 12345
When this SSRS report is exported into Word file, the output still looks the same. However if you look closely you will see at the end of line we have 'line feed' and 'carriage return character'. With data if you tried to use Mail-Envelop facility then the address doesn't comes into address box automatically.
1234 SomeRoad↵
SomeOther Address↵
SomeCity 12345↵
If we change these 'return characters' into paragraph Symbols manually. By going at the end of each line and press delete(the next line comes up) and then press enter(the addressline goes to line below again). This will remove the return character(↵) to paragraph character (¶). Then if you go to mail-Envelope option then address will be populated properly.
1234 SomeRoad¶
SomeOther Address¶
SomeCity 12345¶
Approaches we have tried:
- Used variations with chr(10) and chr(13), every time the problem comes to same formatting.
- Tried to insert paragraph character directly from SQL by using chr(0182). This inserts paragraph symbol but it is treated as special character(Comes as it is) and not the actual paragraph symbol from the word.
Please suggest if there is other way to resolve this problem. Or if there is better approach to satisfy the requirement itself.
Thanks.
reporting-services ms-word oracle-sqldeveloper envelope
add a comment |
We are trying to providing MS-Word's Mail-Envelope facility to end users.
Address is being fetched from oracle database as below:
AddressLine1 || chr(10) || chr(13) ||
AddressLine2 || chr(10) || chr(13) ||
CityAndZip || chr(10) || chr(13) as Address
Then in SSRS report output is showing like this, which is expected:
1234 SomeRoad
SomeOther Address
SomeCity 12345
When this SSRS report is exported into Word file, the output still looks the same. However if you look closely you will see at the end of line we have 'line feed' and 'carriage return character'. With data if you tried to use Mail-Envelop facility then the address doesn't comes into address box automatically.
1234 SomeRoad↵
SomeOther Address↵
SomeCity 12345↵
If we change these 'return characters' into paragraph Symbols manually. By going at the end of each line and press delete(the next line comes up) and then press enter(the addressline goes to line below again). This will remove the return character(↵) to paragraph character (¶). Then if you go to mail-Envelope option then address will be populated properly.
1234 SomeRoad¶
SomeOther Address¶
SomeCity 12345¶
Approaches we have tried:
- Used variations with chr(10) and chr(13), every time the problem comes to same formatting.
- Tried to insert paragraph character directly from SQL by using chr(0182). This inserts paragraph symbol but it is treated as special character(Comes as it is) and not the actual paragraph symbol from the word.
Please suggest if there is other way to resolve this problem. Or if there is better approach to satisfy the requirement itself.
Thanks.
reporting-services ms-word oracle-sqldeveloper envelope
We are trying to providing MS-Word's Mail-Envelope facility to end users.
Address is being fetched from oracle database as below:
AddressLine1 || chr(10) || chr(13) ||
AddressLine2 || chr(10) || chr(13) ||
CityAndZip || chr(10) || chr(13) as Address
Then in SSRS report output is showing like this, which is expected:
1234 SomeRoad
SomeOther Address
SomeCity 12345
When this SSRS report is exported into Word file, the output still looks the same. However if you look closely you will see at the end of line we have 'line feed' and 'carriage return character'. With data if you tried to use Mail-Envelop facility then the address doesn't comes into address box automatically.
1234 SomeRoad↵
SomeOther Address↵
SomeCity 12345↵
If we change these 'return characters' into paragraph Symbols manually. By going at the end of each line and press delete(the next line comes up) and then press enter(the addressline goes to line below again). This will remove the return character(↵) to paragraph character (¶). Then if you go to mail-Envelope option then address will be populated properly.
1234 SomeRoad¶
SomeOther Address¶
SomeCity 12345¶
Approaches we have tried:
- Used variations with chr(10) and chr(13), every time the problem comes to same formatting.
- Tried to insert paragraph character directly from SQL by using chr(0182). This inserts paragraph symbol but it is treated as special character(Comes as it is) and not the actual paragraph symbol from the word.
Please suggest if there is other way to resolve this problem. Or if there is better approach to satisfy the requirement itself.
Thanks.
reporting-services ms-word oracle-sqldeveloper envelope
reporting-services ms-word oracle-sqldeveloper envelope
asked Nov 15 at 22:45
Sandip Pawar
63
63
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The paragraph symbol in Word is ANSI 13, only. Any other combination, such as the ANSI 10 + ANSI 13 you're currently exporting to Word, will not be recognized correctly. Simply strip out the ANSI 10 and you should get the expected result.
We have already tried with only chr(13). It didn't help. Also as I mentioned chr(13) is giving carriage return but not the paragraph symbol. Paragraph symbol only appears when you actually press enters in word doc.
– Sandip Pawar
Nov 19 at 22:21
@SandipPawar No, you don't mention any of that in your question. But in any case. ANSI 13 is what generates the paragraph symbol in Word documents. If you don't believe me, open a Word document (a "real" one, not one generated by a tool), select the paragraph mark, then run ` ?Asc(Selection.Text)` in the Immediate Window of the VBA Editor. Possibly these documents contain other content that's causing a problem.
– Cindy Meister
Nov 19 at 22:41
thanks for your response. I believe you regarding fact about chr(13). In the approaches I had mention that we have tired few combination with chr(10) and chr(13). So initially we tried only with chr(13), because we were expecting that it will give us the next line. It does give a next line. However it is not giving the paragraph symbol when we export the SSRS report output into word. It shows (↵) character. With this visually we see address lines are on separate lines. However mail-envelope is failing to pickup the address correctly.
– Sandip Pawar
Nov 20 at 14:48
I verified for other characters, they are no other special characters. So when we export SSRS report to word, may be SSRS is interpreting these chr(13) to (↵) and not the (¶).
– Sandip Pawar
Nov 20 at 15:02
I'm not familiar with SSRS, but just for information the symbol you show with the arrow usually denotes ANSI 11. If yoiu can confirm they are ANSI 11 (or any other specific character) it would be possible to use Find/Replace in Word to replace them with the "right" paragraph mark if SSRS won't export in a format Word prefers.
– Cindy Meister
Nov 20 at 16:26
add a comment |
Alright, so what we have used is placeholders in SSRS report. Insider text box, put some placeholders, that are generating '¶' and next line when export into word. You can add some static text along with placeholders(for dynamic data). With this we don't need to change SQL for getting data in particular format.
E.g.
Address:
[Placeholder-AddressLine1],
[Placeholder-AddressLine2]
[Placeholder-CityAndZip]
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53328935%2foracle-sql-ssrs-output-ms-word-envelop-formatting-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The paragraph symbol in Word is ANSI 13, only. Any other combination, such as the ANSI 10 + ANSI 13 you're currently exporting to Word, will not be recognized correctly. Simply strip out the ANSI 10 and you should get the expected result.
We have already tried with only chr(13). It didn't help. Also as I mentioned chr(13) is giving carriage return but not the paragraph symbol. Paragraph symbol only appears when you actually press enters in word doc.
– Sandip Pawar
Nov 19 at 22:21
@SandipPawar No, you don't mention any of that in your question. But in any case. ANSI 13 is what generates the paragraph symbol in Word documents. If you don't believe me, open a Word document (a "real" one, not one generated by a tool), select the paragraph mark, then run ` ?Asc(Selection.Text)` in the Immediate Window of the VBA Editor. Possibly these documents contain other content that's causing a problem.
– Cindy Meister
Nov 19 at 22:41
thanks for your response. I believe you regarding fact about chr(13). In the approaches I had mention that we have tired few combination with chr(10) and chr(13). So initially we tried only with chr(13), because we were expecting that it will give us the next line. It does give a next line. However it is not giving the paragraph symbol when we export the SSRS report output into word. It shows (↵) character. With this visually we see address lines are on separate lines. However mail-envelope is failing to pickup the address correctly.
– Sandip Pawar
Nov 20 at 14:48
I verified for other characters, they are no other special characters. So when we export SSRS report to word, may be SSRS is interpreting these chr(13) to (↵) and not the (¶).
– Sandip Pawar
Nov 20 at 15:02
I'm not familiar with SSRS, but just for information the symbol you show with the arrow usually denotes ANSI 11. If yoiu can confirm they are ANSI 11 (or any other specific character) it would be possible to use Find/Replace in Word to replace them with the "right" paragraph mark if SSRS won't export in a format Word prefers.
– Cindy Meister
Nov 20 at 16:26
add a comment |
The paragraph symbol in Word is ANSI 13, only. Any other combination, such as the ANSI 10 + ANSI 13 you're currently exporting to Word, will not be recognized correctly. Simply strip out the ANSI 10 and you should get the expected result.
We have already tried with only chr(13). It didn't help. Also as I mentioned chr(13) is giving carriage return but not the paragraph symbol. Paragraph symbol only appears when you actually press enters in word doc.
– Sandip Pawar
Nov 19 at 22:21
@SandipPawar No, you don't mention any of that in your question. But in any case. ANSI 13 is what generates the paragraph symbol in Word documents. If you don't believe me, open a Word document (a "real" one, not one generated by a tool), select the paragraph mark, then run ` ?Asc(Selection.Text)` in the Immediate Window of the VBA Editor. Possibly these documents contain other content that's causing a problem.
– Cindy Meister
Nov 19 at 22:41
thanks for your response. I believe you regarding fact about chr(13). In the approaches I had mention that we have tired few combination with chr(10) and chr(13). So initially we tried only with chr(13), because we were expecting that it will give us the next line. It does give a next line. However it is not giving the paragraph symbol when we export the SSRS report output into word. It shows (↵) character. With this visually we see address lines are on separate lines. However mail-envelope is failing to pickup the address correctly.
– Sandip Pawar
Nov 20 at 14:48
I verified for other characters, they are no other special characters. So when we export SSRS report to word, may be SSRS is interpreting these chr(13) to (↵) and not the (¶).
– Sandip Pawar
Nov 20 at 15:02
I'm not familiar with SSRS, but just for information the symbol you show with the arrow usually denotes ANSI 11. If yoiu can confirm they are ANSI 11 (or any other specific character) it would be possible to use Find/Replace in Word to replace them with the "right" paragraph mark if SSRS won't export in a format Word prefers.
– Cindy Meister
Nov 20 at 16:26
add a comment |
The paragraph symbol in Word is ANSI 13, only. Any other combination, such as the ANSI 10 + ANSI 13 you're currently exporting to Word, will not be recognized correctly. Simply strip out the ANSI 10 and you should get the expected result.
The paragraph symbol in Word is ANSI 13, only. Any other combination, such as the ANSI 10 + ANSI 13 you're currently exporting to Word, will not be recognized correctly. Simply strip out the ANSI 10 and you should get the expected result.
answered Nov 16 at 6:55
Cindy Meister
14.1k102134
14.1k102134
We have already tried with only chr(13). It didn't help. Also as I mentioned chr(13) is giving carriage return but not the paragraph symbol. Paragraph symbol only appears when you actually press enters in word doc.
– Sandip Pawar
Nov 19 at 22:21
@SandipPawar No, you don't mention any of that in your question. But in any case. ANSI 13 is what generates the paragraph symbol in Word documents. If you don't believe me, open a Word document (a "real" one, not one generated by a tool), select the paragraph mark, then run ` ?Asc(Selection.Text)` in the Immediate Window of the VBA Editor. Possibly these documents contain other content that's causing a problem.
– Cindy Meister
Nov 19 at 22:41
thanks for your response. I believe you regarding fact about chr(13). In the approaches I had mention that we have tired few combination with chr(10) and chr(13). So initially we tried only with chr(13), because we were expecting that it will give us the next line. It does give a next line. However it is not giving the paragraph symbol when we export the SSRS report output into word. It shows (↵) character. With this visually we see address lines are on separate lines. However mail-envelope is failing to pickup the address correctly.
– Sandip Pawar
Nov 20 at 14:48
I verified for other characters, they are no other special characters. So when we export SSRS report to word, may be SSRS is interpreting these chr(13) to (↵) and not the (¶).
– Sandip Pawar
Nov 20 at 15:02
I'm not familiar with SSRS, but just for information the symbol you show with the arrow usually denotes ANSI 11. If yoiu can confirm they are ANSI 11 (or any other specific character) it would be possible to use Find/Replace in Word to replace them with the "right" paragraph mark if SSRS won't export in a format Word prefers.
– Cindy Meister
Nov 20 at 16:26
add a comment |
We have already tried with only chr(13). It didn't help. Also as I mentioned chr(13) is giving carriage return but not the paragraph symbol. Paragraph symbol only appears when you actually press enters in word doc.
– Sandip Pawar
Nov 19 at 22:21
@SandipPawar No, you don't mention any of that in your question. But in any case. ANSI 13 is what generates the paragraph symbol in Word documents. If you don't believe me, open a Word document (a "real" one, not one generated by a tool), select the paragraph mark, then run ` ?Asc(Selection.Text)` in the Immediate Window of the VBA Editor. Possibly these documents contain other content that's causing a problem.
– Cindy Meister
Nov 19 at 22:41
thanks for your response. I believe you regarding fact about chr(13). In the approaches I had mention that we have tired few combination with chr(10) and chr(13). So initially we tried only with chr(13), because we were expecting that it will give us the next line. It does give a next line. However it is not giving the paragraph symbol when we export the SSRS report output into word. It shows (↵) character. With this visually we see address lines are on separate lines. However mail-envelope is failing to pickup the address correctly.
– Sandip Pawar
Nov 20 at 14:48
I verified for other characters, they are no other special characters. So when we export SSRS report to word, may be SSRS is interpreting these chr(13) to (↵) and not the (¶).
– Sandip Pawar
Nov 20 at 15:02
I'm not familiar with SSRS, but just for information the symbol you show with the arrow usually denotes ANSI 11. If yoiu can confirm they are ANSI 11 (or any other specific character) it would be possible to use Find/Replace in Word to replace them with the "right" paragraph mark if SSRS won't export in a format Word prefers.
– Cindy Meister
Nov 20 at 16:26
We have already tried with only chr(13). It didn't help. Also as I mentioned chr(13) is giving carriage return but not the paragraph symbol. Paragraph symbol only appears when you actually press enters in word doc.
– Sandip Pawar
Nov 19 at 22:21
We have already tried with only chr(13). It didn't help. Also as I mentioned chr(13) is giving carriage return but not the paragraph symbol. Paragraph symbol only appears when you actually press enters in word doc.
– Sandip Pawar
Nov 19 at 22:21
@SandipPawar No, you don't mention any of that in your question. But in any case. ANSI 13 is what generates the paragraph symbol in Word documents. If you don't believe me, open a Word document (a "real" one, not one generated by a tool), select the paragraph mark, then run ` ?Asc(Selection.Text)` in the Immediate Window of the VBA Editor. Possibly these documents contain other content that's causing a problem.
– Cindy Meister
Nov 19 at 22:41
@SandipPawar No, you don't mention any of that in your question. But in any case. ANSI 13 is what generates the paragraph symbol in Word documents. If you don't believe me, open a Word document (a "real" one, not one generated by a tool), select the paragraph mark, then run ` ?Asc(Selection.Text)` in the Immediate Window of the VBA Editor. Possibly these documents contain other content that's causing a problem.
– Cindy Meister
Nov 19 at 22:41
thanks for your response. I believe you regarding fact about chr(13). In the approaches I had mention that we have tired few combination with chr(10) and chr(13). So initially we tried only with chr(13), because we were expecting that it will give us the next line. It does give a next line. However it is not giving the paragraph symbol when we export the SSRS report output into word. It shows (↵) character. With this visually we see address lines are on separate lines. However mail-envelope is failing to pickup the address correctly.
– Sandip Pawar
Nov 20 at 14:48
thanks for your response. I believe you regarding fact about chr(13). In the approaches I had mention that we have tired few combination with chr(10) and chr(13). So initially we tried only with chr(13), because we were expecting that it will give us the next line. It does give a next line. However it is not giving the paragraph symbol when we export the SSRS report output into word. It shows (↵) character. With this visually we see address lines are on separate lines. However mail-envelope is failing to pickup the address correctly.
– Sandip Pawar
Nov 20 at 14:48
I verified for other characters, they are no other special characters. So when we export SSRS report to word, may be SSRS is interpreting these chr(13) to (↵) and not the (¶).
– Sandip Pawar
Nov 20 at 15:02
I verified for other characters, they are no other special characters. So when we export SSRS report to word, may be SSRS is interpreting these chr(13) to (↵) and not the (¶).
– Sandip Pawar
Nov 20 at 15:02
I'm not familiar with SSRS, but just for information the symbol you show with the arrow usually denotes ANSI 11. If yoiu can confirm they are ANSI 11 (or any other specific character) it would be possible to use Find/Replace in Word to replace them with the "right" paragraph mark if SSRS won't export in a format Word prefers.
– Cindy Meister
Nov 20 at 16:26
I'm not familiar with SSRS, but just for information the symbol you show with the arrow usually denotes ANSI 11. If yoiu can confirm they are ANSI 11 (or any other specific character) it would be possible to use Find/Replace in Word to replace them with the "right" paragraph mark if SSRS won't export in a format Word prefers.
– Cindy Meister
Nov 20 at 16:26
add a comment |
Alright, so what we have used is placeholders in SSRS report. Insider text box, put some placeholders, that are generating '¶' and next line when export into word. You can add some static text along with placeholders(for dynamic data). With this we don't need to change SQL for getting data in particular format.
E.g.
Address:
[Placeholder-AddressLine1],
[Placeholder-AddressLine2]
[Placeholder-CityAndZip]
add a comment |
Alright, so what we have used is placeholders in SSRS report. Insider text box, put some placeholders, that are generating '¶' and next line when export into word. You can add some static text along with placeholders(for dynamic data). With this we don't need to change SQL for getting data in particular format.
E.g.
Address:
[Placeholder-AddressLine1],
[Placeholder-AddressLine2]
[Placeholder-CityAndZip]
add a comment |
Alright, so what we have used is placeholders in SSRS report. Insider text box, put some placeholders, that are generating '¶' and next line when export into word. You can add some static text along with placeholders(for dynamic data). With this we don't need to change SQL for getting data in particular format.
E.g.
Address:
[Placeholder-AddressLine1],
[Placeholder-AddressLine2]
[Placeholder-CityAndZip]
Alright, so what we have used is placeholders in SSRS report. Insider text box, put some placeholders, that are generating '¶' and next line when export into word. You can add some static text along with placeholders(for dynamic data). With this we don't need to change SQL for getting data in particular format.
E.g.
Address:
[Placeholder-AddressLine1],
[Placeholder-AddressLine2]
[Placeholder-CityAndZip]
answered Dec 11 at 18:21
Sandip Pawar
63
63
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53328935%2foracle-sql-ssrs-output-ms-word-envelop-formatting-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown