Hi,
  I need to access to my ANSI database (non unicode) form Visual C# or Studio .NET..

I have tried by "non unicode ODBC"  but the application fails
instead
"unicode ODBC" doesn't accept password and I can't create DSN.

is this possible or I must use an Unicode Database ??

Thank you

Dario

Dario,

<< is this possible or I must use an Unicode Database ?? >>

..NET is 100% Unicode, so you must use a Unicode database.

--
Tim Young
Elevate Software
www.elevatesoft.com

Right

But is there something like a layer (for example remobjects or other Third Party) to interface NET to "EDB ODBC (non unicode)" ??

I have my project that works with non-unicode database and other people need to access too but they are developing in Visual C#..

I have thinked to convert my DB in unicode..
is my source code 100% compatible ?? I think no but my know-how is really low

this question because it seems to be a different TField declaration fro example:
TWideStringField instead TStringField
TWideMemoField instead TMemoField

Thank you

Dario




"Tim Young [Elevate Software]" wrote:

Dario,

<< is this possible or I must use an Unicode Database ?? >>

..NET is 100% Unicode, so you must use a Unicode database.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dario,

<< But is there something like a layer (for example remobjects or other
Third Party) to interface NET to "EDB ODBC (non unicode)" ?? >>

Not that I'm aware of.

<< I have my project that works with non-unicode database and other people
need to access too but they are developing in Visual C#..

I have thinked to convert my DB in unicode.. >>

That's your best solution, since it will enable any .NET application to be
able to access your database without any issues.

<< is my source code 100% compatible ?? I think no but my know-how is really
low >>

this question because it seems to be a different TField declaration fro
example:
TWideStringField instead TStringField
TWideMemoField instead TMemoField >>

Except for the field types, yes, the source code is 100% compatible.  You
will essentially have to re-create any persistent fields using the fields
editor after converting the database to Unicode.


--
Tim Young
Elevate Software
www.elevatesoft.com