Re: Trouble importing foreign language accents into Access 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Just saw your message. Beside with or without BOM, there are two types of
UTF-16 (for a total combination of four). Did you try the other
possibilities as well? It can also have another name such as simply
Unicode.

I don't know Ultra-Edit, so I'm not really sure if your problem is with
Ultra-Edit or with the importation routine.

Also, when you import data, if you leave it to Access, Access will usually
take a look at only the first 255 characters or so before determining the
encoding of the file. This is possibly what's happening to you when you add
the other fields. You should really specify to Access that this is an
Unicode file. Trying with a specific code page - other than Unicode - could
also help.

I will try to make some tests later but at this moment, I'm reduced to only
make wild guesses about your problem.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
Independent consultant and remote programming for Access and SQL-Server
(French)


"efortin" <efortin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:79B4E7F8-D3E5-477C-BFD3-E52F1065AF31@xxxxxxxxxxxxxxxx
Hello again,

I thought the problem was solved but it is not. When I reduce the file
down
to only a field that has the accents, and I save it first in UTF-8, then
close ultra-edit, re-open the file and save it as ANSI/ASCII, the accent
conversion occurs. But when I do the same steps on the whole file, no
accents
are converted. I have also tried UTF-16, with and without BOM.

Any help is much appreciated.

Elaine

"efortin" wrote:

Merci beaucoup, Sylvain!

Saving the file in ANSI/ASCII format solved most of the problems with
foreign characters. I am still getting some junk in the file which Access
complains about, but with good reason. I believe it was some weird
character
keyed by mistake in data entry.

Elaine

"Sylvain Lafontaine" wrote:

When you make a reference to another post, you should give it reference
so
that people can take a look at it and see what you are doing or try to
follow.

In your case, when you see that you accentuated letters have been
replaced
by a combination of two letters, the first one beeing Ã, you must
suspect
that your file is in Unicode 8 bit or utf-8. Try setting your code
page to
65001.

You should also check if your file begin with a BOM (Byte Ordre Marker)
as
its presence or its absence could throw off the Auto-select.

Also, it's quite possible won't be able to import Unicode encoded with
uft-8. If this is the case, re-save your ascii file but this time use
Unicode 16 bit (utf-16) or in another code page. In the case of
utf-16, try
with or without a BOM (also called a signature in some dialog windows).

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
Independent consultant and remote programming for Access and SQL-Server
(French)


"efortin" <efortin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8164EFD5-2423-4120-A2A2-F65494E44DCF@xxxxxxxxxxxxxxxx
Hi,

In an earlier post, a solution to another developer's description of
the
same problem I have was to set the Import Specification to "All"
and Code Page to "Auto-select" .

This solution does not solve the same problem for me. I am importing
a
tab delimited text file into Access 2003, with Import Specification
of
"All"
and Code Page of "Auto-select" ( though I have tried Western Europe
Windows
and several others) to no avail. The text value 'Sören' appears in
Access
as
'Sören' in every case.

Please help!
Thanks,
Elaine


.



.



Relevant Pages

  • Re: Trouble importing foreign language accents into Access 2003
    ... 'All' and for Code Page to be 'Auto-Select', the accents are correct in the ... Unicode file. ... MVP - Windows Live Platform ... I have also tried UTF-16, ...
    (microsoft.public.access.externaldata)
  • Re: Text File problem - VC++ MFC Studio 2008 MFC app
    ... I still don't trust CStdioFile to write text to files... ... That means that the text was not written in Unicode UTF-16, because in UTF-16 there are 2 bytes for each character. ... Moreover, there is no BOM. ...
    (microsoft.public.vc.mfc)
  • Re: problem writing cstring to file
    ... translation of double quotes " character, so: there is no BOM! ... This is a violation of Unicode UTF-16 protocol (a BOM should be the first ... if here are higher level protocols that tag the string as UTF-16LE ...
    (microsoft.public.vc.mfc)
  • Re: unicode in ruby
    ... doesn't support unicode strings natively? ... (When Unix filesystems can write UTF-16 as ... to use decomposed characters instead of composed characters (e.g., ... even compress repetitive text which no encoding can. ...
    (comp.lang.ruby)
  • Re: unicode in ruby
    ... doesn't support unicode strings natively? ... put on Unix ages ago. ... (When Unix filesystems can write UTF-16 as ... translate to UTF-8 and/or follow the nonsensical POSIX rules for native ...
    (comp.lang.ruby)