Subject Re: [IBO] More (perhaps) UTF8 issues
Author Robert Martin
Hi

That's what I initially thought but Its actually the reverse this time.
The field IS defined as TWideStringField but the DB seems to be
returning TFixedChar, which IBO is disallowing.

Thanks
Rob


On 12/09/2013 10:06 a.m., IBO Support List wrote:
> Hi Rob,
>
> IBO is disallowing you to have a persistent field that is incapable of
> displaying unicode data.
>
> You need to do a search and replace in your app like we did before and
> replace TFixedCharField (or whatever it is called) and put TWideStringField
> in its place.
>
> Jason
>
> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com] On Behalf
> Of Robert Martin
> Sent: Wednesday, September 11, 2013 3:59 PM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] More (perhaps) UTF8 issues
>
> Hi Jason
>
> Not sure if this was one of the things we worked through or not but I
> have just run into the following persistent field definition issue.
>
> Database : FB 2.5.2
> Defualt DB Character set : UTF8
> Error : Query : Type mismatch for field 'Completed', expecting:
> WideString actual: FixedChar
>
> The Query field is defined as TWideStringField
>
> The SQL for the query is the following
>
> SELECT GlTransRef, TransDate, Ref, Detail, ExportStatus , Completed
> FROM vwALLGLTrans
> WHERE ExportStatus IS NULL
>
>
> vwALLGLTrans is a view that is defined as follows...
>
> CREATE VIEW vwAllGLTrans (GLTransRef, TransDate, Ref, Detail,
> SEntityRef, BatchDate, BatchTime, PeriodNum, MEntityRef, PostedFrom,
> BEntityRef, ImportRef, ExportStatus, Completed) AS
> SELECT GLTransRef, TransDate, Ref, Detail, SEntityRef, BatchDate,
> BatchTime, PeriodNum, MEntityRef, PostedFrom, BEntityRef, ImportRef,
> ExportStatus, 'F'
> FROM GLTrans
> UNION ALL
> SELECT GLTransRef, TransDate, Ref, Detail, SEntityRef, BatchDate,
> BatchTime, PeriodNum, MEntityRef, PostedFrom, BEntityRef, ImportRef,
> ExportStatus, 'T'
> FROM GLCompletedTrans^
>
>
> It appears that FB is ignoring the database default characterset (UTF8)
> for the Completed field and is returning it as a fixed ansi char instead
> of a fixed UTF8 char (TFixedWideChar).
>
> I'm not sure if this is a FB fault or not.
>
> Any ideas how to get around it?
>
> Thanks
> Rob
>
>
>
>
>
>
> ------------------------------------
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
> http://tracker.ibobjects.com - your portal to submit and monitor bug reports
> http://community.ibobjects.com - your portal to purchase and upgradeYahoo!
> Groups Links
>
>
>
>
>
> ------------------------------------
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
> http://tracker.ibobjects.com - your portal to submit and monitor bug reports
> http://community.ibobjects.com - your portal to purchase and upgradeYahoo! Groups Links
>
>
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3392 / Virus Database: 3222/6656 - Release Date: 09/11/13
>
>