Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COHi Jeffrey, It worked beautifully and I managed to get the desired output (user was prompted to download the .doc file). However, I seem to get my encoding totally wrong. When I open the word document (or change it to a .rtf file), it seems that it cannot recognize the content and asks me how should I encode it. Once I select the encoding (e.g. UTF-8), the file opens and the content is displayed correctly. This is my code: (cont'd)
      singulars
    2. CObegin OWA_UTIL.MIME_HEADER ( 'Content-Type:application/vnd.ms-word;charset=utf-8', false); htp.print('Content-Disposition:attachment;filename="test.doc"'); OWA_UTIL.HTTP_HEADER_CLOSE; for x in (select column_one, column_two from my_table) loop htp.p(x.column_one ||chr(10)||x.column_two ||chr(10)||chr(10)); end loop; htmldb_application.g_unrecoverable_error := true; end; . . . . Any idea where I can change the mime_header to open the file seamlessly? Many thanks
      singulars
    3. COYou'll probably find it will work if you send HTML syntax as the data. e.g. `begin OWA_UTIL.MIME_HEADER ( 'Content-Type:application/vnd.ms-word;charset=utf-8', false); htp.print('Content-Disposition:attachment;filename="test.doc"'); OWA_UTIL.HTTP_HEADER_CLOSE; htp.p('<html><body>'); for x in (select column_one, column_two from my_table) loop htp.p(x.column_one ||'<br>'||x.column_two ||'<br><br>'); end loop; htp.p('</body></html>'); htmldb_application.g_unrecoverable_error := true; end;`
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload