Subject RE: [ibo] tIBOquery Issue
Author Jack Cane
Ye, Daniel, that was it. Works fine, now.

Tks, and holiday greetings,

jwc
-----Original Message-----
From: Daniel Rail [mailto:daniel@...]
Sent: Sunday, December 29, 2002 2:44 PM
To: IBObjects@yahoogroups.com
Subject: Re: [ibo] tIBOquery Issue


Hi,

> My form has three tIBOqueries linked to an FB dataset through a
tIboDataBase
> and three tDataSources. All three queries are set active and the
> tDbNavigators show appropriage buttons enabled.

> One tIBOquery, qPages, is targeted on table TARGETURL. The form has
tdbEdit
> fields connected to fields TARGETNR (the primary key field), TARGETNAME
and
> CONFIGNUM. The latter field is linked to another table via a foreign key
> constraint. All the tdbEdits are linked properly to existing fields in
the
> table, TARGETURL. I can see them in the dropdown for the field name
> property.

> When I run the app., the form stumbles over the following query:

> 'select TargetName from TARGETURL where CONFIGNUM = 1 order by
TargetName'.

> The error is exception class EDatabaseError with message 'edTargetNr:
Field
> 'TARGETNR' not found'.

> I have deleted and rebuilt the tIBOquery, with identical results.

> Any assistance appreciated.

All fields that you'll be using, either in the code or in visual
components, have to be part of the returned result set.

Try with the following query:
select TARGETNR, TargetName from TARGETURL where CONFIGNUM = 1 order by
TargetName


Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.accramed.ca)



___________________________________________________________________________
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 !

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


[Non-text portions of this message have been removed]