Is there a way to identify the record to change if it does not have a unique field.
I see theres mention of RecordID but i cant seem to access it.

In DBISAM 4.x then there is a system field called RecordID - you'd need
to actually specify it for it to show up (i.e. "select RecordID,* from
mytable" for example instead of "select * from mytable").

Raul


On 9/28/2013 11:15 AM, Aaron Taylor wrote:
> Is there a way to identify the record to change if it does not have a unique field.
> I see theres mention of RecordID but i cant seem to access it.
>

Thanks Raul, ill give that a go.

That works well if you do a query, is there a way to get the RecordID if your using a TDBISAMTable.

Im displaying the data by TDBISAMTable and then updating the record via TDBISAMQuery.

Have you tried    .FieldByName('RecordID').AsInteger;

--
Jeff Cook
Aspect Systems Ltd
www.aspect.co.nz

<Aaron Taylor> wrote in message
news:105B05EB-5F39-4E47-B61A-453B3966FAEA@news.elevatesoft.com...
> That works well if you do a query, is there a way to get the RecordID if
> your using a TDBISAMTable.
>
> Im displaying the data by TDBISAMTable and then updating the record via
> TDBISAMQuery.
>

it returns error - field not found.

It's not exposed as part of the dataset fields but you can access it by
using DBISAMTable.RecordID field for the current record.

if you can switch to query instead of table then you can just include it
as part of the field list on select.


Raul


On 9/28/2013 12:49 PM, Aaron Taylor wrote:
> That works well if you do a query, is there a way to get the RecordID if your using a TDBISAMTable.
>
> Im displaying the data by TDBISAMTable and then updating the record via TDBISAMQuery.
>

Aaron,

<< Is there a way to identify the record to change if it does not have a
unique field. I see theres mention of RecordID but i cant seem to access it.
>>

You can use the system-maintained RecordID to identify records, but the
problem is that unless you have an index on the RecordID field, you won't be
able to quickly or efficiently locate records using it.

So, you'll want to, at the very least, define an index on RecordID and then
you can use FindKey, etc. to search on it.

Tim Young
Elevate Software
www.elevatesoft.com