To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=97762
Issue #|97762
Summary|Exporting a base table into CSV text file: Unicode cod
|e replaced by ? sign
Component|Database access
Version|OOO300m7
Platform|Unknown
URL|http://user.services.openoffice.org/en/forum/viewtopic
|.php?f=13&t=5009&st=0&sk=t&sd=a&start=10
OS/Version|Windows XP
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P2
Subcomponent|none
Assigned to|dbaneedsconfirm
Reported by|nbrouard
------- Additional comments from nbrou...@openoffice.org Mon Jan 5 08:19:39
+0000 2009 -------
>From the forum discussion link it appears that a way to export a table from a
base database into a CSV consists in the following steps. It works but ...:
-------------------------Solution quoted-----
To start this ( and, this can also be accomplished by a macro if you so desire )
. . . the steps are:
1. Open your database
2. From the menu: Tools -> SQL...
3. under Command to execute, enter your SQL
4. an example might be ( change output_csv_file_name to your desired OUTPUT
name, and, your_table_name to the HSQL table you are using )
Code: Select all Expand viewCollapse view
SELECT * INTO TEXT "output_csv_file_name" FROM "your_table_name"
5. Press the Execute button
6. Press the Close button
The bottom line . . . this will create a TEXT CSV file for you . . . located in
the same directory where your database ODB file is located. The file will have a
file type of CSV .
Additionally, your database will have a NEW TEXT 'table' as defined by the name
you gave it in the SELECT above. This 'database' file may be deleted.
Also, you can include a WHERE clause above if you wish to only output a part of
the table to your CSV file. And, an ORDER BY clause will further define the CSV
output.
-------------------------
... the problem encountered, even on latest 3.00m7 version is that my accented
characters disappeared. I know that Windows has difficulties is writing text
files in Unicode but I am not sure that it is a Windows problem.
I haven't found an option for the SELECT command or for the INTO TEXT command to
add something like UTF-8 encoding or similar. In both, the .CSV file as well as
the new table created into the database, all accented characters have been
replaced by ? signs.
PS: Priority is set to P2 because last time I used P3 it last more than a year.
I won't be frustrated if you confirm the bug and that if there is no easy work
around to be downgraded to a lower priority.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
