Subject | Re: [IBO] Issue with reserved words in IBO components |
---|---|
Author | Robert Martin |
Post date | 2013-10-30T20:53:31Z |
Hi
Its NOT an IBO issue. I have tested further and it turns out the table
had a filter defined as ' Type = 'R' ', changing it to ' "Type" = 'R' '
fixes the problem !
My apologies for any time spent tracking this down!
Thanks
Rob
Its NOT an IBO issue. I have tested further and it turns out the table
had a filter defined as ' Type = 'R' ', changing it to ' "Type" = 'R' '
fixes the problem !
My apologies for any time spent tracking this down!
Thanks
Rob
On 30/10/2013 3:10 p.m., Robert Martin wrote:
> Hi Jason
>
> In the latest release when opening a TIBOTable component where the
> underlying table has a reserved word that is NOT defined all uppercase
> the table crashes with field not found. The component doesn't have any
> persistent fields defined (I think it works if it does).
>
> The underlying field is defined as "Type". I know the 'standard' for
> Firebird is defined reserved words as all uppercase but this is not a
> requirement and in our case we foolishly defined them as mixed case.
>
> I am on Skype now if you want to have a look at it.
>
> Cheers
> 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
>
>
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3426 / Virus Database: 3222/6792 - Release Date: 10/29/13
>
>