Hi Sven

I had no idea you could use the double quotes in the FieldByName()
call!! guess that's becuase I never had to in the past. Yes the field
is defined as "Rows" in the DB. Will have to have a look and see which
is easier

a) Change DB to "ROWS" and check all SQLs and change them

or

b) Do a find and replace on ('Rows') and change it to ('"Rows"')


b) seems easier and safer in the short term but not very nice !

Cheers
Rob

On 17/06/2013 5:58 p.m., Svein Erling Tysvær wrote:
>> Hi Helen
>>
>> Thanks. I understand the issues and agree that generally reserved words should be avoided like the plague. The only fields that are quoted in
>> our DB are reserved words that were defined before the database was a Firebird database !
>>
>> All our SQL is correct and working, the database version has not changed, the issue is with IBO. Previously (IBO 4.8) code like
>>
>> Query.FieldByName('Rows').AsInteger
>>
>> worked perfectly. Now this code returns a 'Field not found' exception (IBO 5.2). This is obviously a code change between IBO versions and I
>> was hoping that Jason would be able to help me out with this.
> But is the field defined as "Rows" or "ROWS" in Firebird? I would assume Query.FieldByName('Rows').AsInteger to match "ROWS", to make it match "Rows", I'd assume you'd have to change to Query.FieldByName('"Rows"').AsInteger.
>
> Set
>
>
> ------------------------------------
>
> ___________________________________________________________________________
> 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 ! Yahoo! Groups Links
>
>
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3345 / Virus Database: 3199/6418 - Release Date: 06/17/13
>
>