.Net Codepage 850 problem with uppercase accented characters

  • Thread starter Thread starter Guest
  • Start date Start date
Hi Jon. It is actually the Microsoft .Net Managed provider for Oracle that we were using and now we are using the Micorosft OLE DB provider for Oracle (which works fine). Another techie has tried Oracle's ODP provider for .Net, which is Oracle's latest offering and he was having problems with it as well. I do not know this forum well, but is this a place where Microsoft will become aware of the .Net managed provider issue and hopefully fix it in the near future??? I reached this forum through an MSDN support link. Just to ensure you understand, it IS the MICROSOFT .Net Managed Provider for Oracle that was not handling codepage 850 well at all

Anyway, both the Oracle ODBC driver AND the Microsoft OLE DB provider for Oracle work fine in our ASP apps, but I choose to use the Microsoft driver for this new ASP.Net app, until such time as the .Net Managed Provider works properly. It will give us better performance than the OLE DB driver. As I mentioned, if anyone from Microsoft needs any more details from me, they can contact me via email (from the one email I sent you). Thanks for your help. --- Barrie
 
Barrie Gray said:
Hi Jon. It is actually the Microsoft .Net Managed provider for Oracle
that we were using and now we are using the Micorosft OLE DB provider
for Oracle (which works fine). Another techie has tried Oracle's ODP
provider for .Net, which is Oracle's latest offering and he was
having problems with it as well.
Right.

I do not know this forum well, but
is this a place where Microsoft will become aware of the .Net managed
provider issue and hopefully fix it in the near future??? I reached
this forum through an MSDN support link. Just to ensure you
understand, it IS the MICROSOFT .Net Managed Provider for Oracle that
was not handling codepage 850 well at all.
Click to expand...

There are certainly some Microsoft employees reading this forum,
although I don't know whether any of them are in an appropriate
position to raise this. If you post a short summary of your findings on
the adonet newsgroup, that may well have more appropriate readers.
Anyway, both the Oracle ODBC driver AND the Microsoft OLE DB provider
for Oracle work fine in our ASP apps, but I choose to use the
Microsoft driver for this new ASP.Net app, until such time as the
.Net Managed Provider works properly. It will give us better
performance than the OLE DB driver. As I mentioned, if anyone from
Microsoft needs any more details from me, they can contact me via
email (from the one email I sent you). Thanks for your help. ---
Barrie
Click to expand...

Um, I'm not from Microsoft, so no-one in Microsoft has the email that
you sent me at the moment. However, presumably if someone from
Microsoft sees this, they could post here and hook up that way.

If you want me to take this further through MVP channels, I'll see what
I can do, but I can't say I've had much contact with the ADO.NET team
before.
 
Barrie Gray said:
Hi Jon. It would be a shame if someone from Microsoft did not pursue
this further. Where do you suggest I post the synopsis of our thread
here? At the least, I could point them at this thread for the details
of our "conversation". I would be happy to provide further
information to anyone from Microsoft who might be able to fix the
provider problem(s). --- B.
Click to expand...

I suggest you post the synopsis of the thread to
microsoft.public.dotnet.framework.adonet, pointing people at this
thread too, as you say. If that doesn't help, I'll see what I can do.
 
Back
Top