OEM ANSI problems.



We are accessing our MSSQL server database with a TADOConnection + TADOQuery
object. The problem is that the returned texts is in OEM format, and we need
to manually convert them to ANSI.

Is there a clever way to do this in one place, for the whole application at
once (I have subclassed TADOQuery, but it seems hard to subclass the
"TMyAdoQuery.FieldByName('MyField').AsString" method).

I have tried the "AutoTranslate=true" connection string property, but this
did not work.


P.s. Converting the database from OEM to ANSI is not an option because about
130 other programs depend on the database beeing in OEM format.

TIA
Karl


.



Relevant Pages

  • Re: Losing the value of a field
    ... but unfortunately I cant change the database. ... I'd like to know if I use the TADOQuery with 'locktype' property set to ... 'batchoptimistc' (what means that the chages will ramain local and are not ...
    (borland.public.delphi.database.ado)
  • Re: Reopening/changing DB at runtime
    ... Check that TADOTable and TADOQuery are connected to ADOConn using Connection ... > I want to provide for the user changing their active database at runtime. ... Similar code as above for the other grids ...
    (borland.public.delphi.database.ado)
  • Re: MSAccess and ADO
    ... database I use TADOQuery and SQL ... Stanko. ...
    (borland.public.delphi.database.ado)
  • Re: ADOQuery and decimal fields in Delphi 5...
    ... You said you where using TadoQuery. ... TADOQuery has an EnableBCD property ... Delphi application to a MS-SQL 2000 database. ... has only 4 digits to the right of the decimal point. ...
    (borland.public.delphi.database.ado)
  • I get an Error message.........
    ... I have set "lookup field" at TADOQuery. ... unknown error has occurred". ... Can TADOQuery input data to database? ...
    (borland.public.delphi.database.ado)