"Alt255" <alt255.2005@gmail.com> wrote in message
news:1147873711.139122.22520@38g2000cwa.googlegrou ps.com...
> Hi Laurenze,
>
> I guess I have to elaborate on my situation. I'm a contractor for a
> large organization using MS Access to create reports from a Oracle Data
> Warehouse used through-out the corporation. I am the System Analyst
> here and cannot create a new database ( though I have my own sandbox).
> I must use the existing tables with the French fields. I would create a
> local table in Access, but some of our product tables ( with French
> descriptions) have 50,000 records changing regularly.
> I have been considering using Impromptu to create a daily extract, and
> then load this into an Access table, but as we know this is a poor
> approach ( but if I cannot resolve this then I must).
>
> I find it baffling that Impromptu can report the correct characters,
> but MS access and Excel cannot. It was this line of thinking that made
> me request a Microsoft resource.
>
> I hate wasting peoples time, Laurenz, are you certain MS cannot help? I
> was in contact with our Senior Oracle DBA initially for a solution but
> he couldn't help. I'm thinking I should show him this thread, maybe
> his knowledge and your suggestions can get this resolved.
>

The problem is putting the wrong sized characters in a database that can't
handle it. (because of the initial wrong set up of the database)
Jim

Microsoft resolve the problem. If I use the MS ODBC for Oracle driver,
the characters are translated properly.
Traditionally analysts such as myself use Oracles ODBC drivers for
performance gain. The initial linking to Oracle using Microsofts driver
take 2 minutes ( as opposed to 20 seconds with Oracle) but I'm more
than willing to suffer this because this delay only impacts me during
development, and shouldn't affect the end users.

Thanks for everyones help, this was a real stumper for us.

Jim Kennedy schreef:

> The problem is putting the wrong sized characters in a database that can't
> handle it. (because of the initial wrong set up of the database)
> Jim

I already have proven the accented e is stored correctly (dump returns
233, or 0xE9).
It is the front end that does weird things - this was resolved by
using a different ODBC driver, but I suspect a different font and code
page could have resolved it as well.

--
Regards,
Frank van Bortel

Top-posting is one way to shut me up...

Come on people! Considering an Oracle ODBC driver fixing this problem
is like putting makeup over plague boils. Get that "Senior DBA" in for
some proper boiling oil treatment.

jg
--
@home.com is bogus.
http://www.themystica.com/mystica/ar...aracelsus.html