This question is locked. New answers and comments are not allowed.
Hi
I reverse engineered a Table named "TGerät".
Reverse Engineering crashed, created false code, which I could repair.
But queries with OQL crash all the time: Telerik.OpenAccess.Exceptions.QueryException: line 1:19: unexpected char: 0xE4
How could I solve this problem?
Thanks in advance
Urs Scherrer
I reverse engineered a Table named "TGerät".
Reverse Engineering crashed, created false code, which I could repair.
But queries with OQL crash all the time: Telerik.OpenAccess.Exceptions.QueryException: line 1:19: unexpected char: 0xE4
How could I solve this problem?
Thanks in advance
Urs Scherrer
2 Answers, 1 is accepted
0
Urs
Top achievements
Rank 2
Rank 2
answered on 13 May 2009, 09:10 AM
Ok, One Solution is to rename the class only: e.g. TGeraet
Also Properties have to be cleaned then it is working.
Will this be fixed in future?
Also Properties have to be cleaned then it is working.
Will this be fixed in future?
0
Hi Urs,
The workaround you mentioned is the right one - to remove the umlaut from the table/field names.
OpenAccess currently does not support OQL queries with identifiers (table/field/property names) having characters other than 'a-z/A-Z,0-9,_' . LINQ queries would however work.
Support for other unicode characters involves a considerable amount of work and is currently not scheduled.
Best wishes,
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
The workaround you mentioned is the right one - to remove the umlaut from the table/field names.
OpenAccess currently does not support OQL queries with identifiers (table/field/property names) having characters other than 'a-z/A-Z,0-9,_' . LINQ queries would however work.
Support for other unicode characters involves a considerable amount of work and is currently not scheduled.
Best wishes,
Ady
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.