Version 9 - What's new - Store INTO plain text file

[#1]

Hello !

I've seen that on version 9 we can dump a table onto a plain text file.

Always wanted that mostly to check how the load process was.

But I noticed that there are weird characters on the beginning of the output file.

On the attached kit you can see the problem by running the load process and then checking the 'test122.txt' output file.

Thanks !

[hector]

It works fine to me

NAME_TEST;DATE_TEST;TIME_TEST;VALUE_TEST
MARY;01/01/2008;00:12:14;200
MARY;01/02/2008;00:12:15;200
ANN;04/01/2008;15:12:25;300
MARY;01/01/2009;00:20:20;210
JOHN;31/12/2008;14:20:30;100

rgds

[#3]

on my machine, the output file is :

NAME_TEST;DATE_TEST;TIME_TEST;VALUE_TEST
MARY;01/01/2008;00:12:14;200
MARY;01/02/2008;00:12:15;200
ANN;04/01/2008;15:12:25;300
MARY;01/01/2009;00:20:20;210
JOHN;31/12/2008;14:20:30;100

it looks fine

[#4]

Please open the file NOT ON NOTEPAD !

LOL

Open the file on an editor that SHOWS you the weird characters !

I use TSE/32 but one can use TextPAD or whatever.

I can see that the file begins with character # 239 from ASCII table then followed by character # 187 and then char # 191. Then comes the header...

[hector]

hi again, i've opened it with, notepad, notepad++, wordpad and i can't see nothing!! LOL

But, with EDIT from DOS, i see this image

do you suggest any other text editor?

rgds

[#6]

oh ok

it's simply not an ASCII text file

sometimes the first bytes in text files are used to specify used encoding

unfortunately i'm far from being an expert in text encoding, so i can't give you any details

[#7]

you can view the weird characters in notepad++ in hexadecimal mode

[#8]

So, by simply using EDIT, you can see the weird characters.

AFAIK that is not a plain ASCII file.

Or is that part of the UTF-8 specification ?

[rwunderlich]

The x'EFBBBF' at eh beginning of the file if the UTF-8 "Byte Order Mark" (BOM) http://en.wikipedia.org/wiki/Byte_order_mark .

I'm not clear on exactly how the new STORE to txt feature is supposed to work, but I would guess that if you specify ANSI or OEM in the format spec there would be no BOM. Don't know that for a fact though. You may want to run this by support if the BOM is causing you problems.

-Rob

[rbecher]

Rob,

I'm facing the same problem. Where do I specify ANSI or OEM in the format spec?

- Ralf