I appologize for the confusion.  We have a Turbo Image database. We also use
Transact as the programming language.  The RECNO I'm referring to is listed as
one of the options under FIND, GET, and DELETE in the Transact manual and
DBFIND, DBGET and DBDELETE in the Turbo Image manual. I should have been more
clear on this.

I came from an IBM mainframe shop using ADABAS and ADABAS uses what it call
ISN's or Internal Sequence Numbers.  These ISN's are automatically generated
by ADABAS at the time a record is created/added to the database and remain
with that record for it's entire life in the database. I was hoping that RECNO
in Turbo Image acted the same way.

The records I'm trying to delete are part of detailed sets not masters.  We
have a poorly designed database and the only way to identify the record to be
deleted is by doing a serial read.  Since I need to delete 80,000 records this
will require separate serial reads on a file of 500,000 records.  To me this
is very inefficient.  That's why I was asking if RECNO (as described in the
Turbo Image Manual) remains constant through the life of the record.

The question still remains... Does RECNO (the 32-bit integer used by Turbo
Image) remain with the record for the life of that record while exists withing
the Turbo Image database.  As far as I can tell we DO NOT repack the database
using any kind of utility.

Thanks again,


> > It took me a little while to understand what you were asking, but I
eventually
> > deduced that RECNO is a data item in an IMAGE database.
>
> With due respect, sir, I think Michael is referring to the
> 32-bit IMAGE
> record number (see DBGET mode 4).  If he builds a list of
> these record numbers
> now and does a DBGET mode 4 followed by a DBDELETE on
> those numbers sometime
> with in the Atmarian month, can he be assured of deleting
> the correct records?

GySgt Michael J. Riley
[log in to unmask]