Hi,

IIRC, the property recno for TEDBDatasets was not going to be populated
correctly for ElevateDB. I'm just thinking ahead here for when I port by
applications from DBISam to EDB - is there a preferred recommendation for an
alternative use to .recno, if I need to obtain the record number?

Thanks & Regards

Adam.

"Adam H." <ahairsub4@rREMOVEMEspamSTOPPER.jvxp.com> wrote in message
news:2C8846CC-7142-4383-8C1F-2690AE3B5792@news.elevatesoft.com...
> Hi,
>
> IIRC, the property recno for TEDBDatasets was not going to be populated
> correctly for ElevateDB. I'm just thinking ahead here for when I port by
> applications from DBISam to EDB - is there a preferred recommendation for
> an alternative use to .recno, if I need to obtain the record number?
>
> Thanks & Regards
>
> Adam.

No idea about DBISam, but we just ported a BDE application to EDB, and we
used RecNo a lot. Days of extra work. It was probably 60-70% of the total
conversion time.

RJ

Adam,

<< IIRC, the property recno for TEDBDatasets was not going to be populated
correctly for ElevateDB. I'm just thinking ahead here for when I port by
applications from DBISam to EDB - is there a preferred recommendation for an
alternative use to .recno, if I need to obtain the record number? >>

It depends upon what you're using the record number for currently - display,
searching, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Steve,

> << IIRC, the property recno for TEDBDatasets was not going to be populated
> correctly for ElevateDB. I'm just thinking ahead here for when I port by
> applications from DBISam to EDB - is there a preferred recommendation for
> an alternative use to .recno, if I need to obtain the record number? >>
>
> It depends upon what you're using the record number for currently -
> display, searching, etc.

I guess most of it is for displaying during routines. If .recordcount still
works, I guess I could look at implementing an inc(x) routine to try and get
past this, or is their another method I should be looking at?

Thanks & Regards

Adam.

Adam,

<< I guess most of it is for displaying during routines. If .recordcount
still works, I guess I could look at implementing an inc(x) routine to try
and get past this, or is their another method I should be looking at? >>

Does the # information really mean anything to the end user, or is it just
for show ?  We usually recommend that you move away from showing a
position/# and into showing the primary key instead.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> Does the # information really mean anything to the end user, or is it just
> for show ?  We usually recommend that you move away from showing a
> position/# and into showing the primary key instead.

It's more for progress bars and so forth when looping through a query for
calculations, etc.

Cheers

Adam.

Adam

>It's more for progress bars and so forth when looping through a query for
>calculations, etc.

In that case I'd just use RecordCount and a variable

Roy Lambert

Adam,

<< It's more for progress bars and so forth when looping through a query for
calculations, etc. >>

In that case, Roy is correct - just use a counter variable and increment it
as necessary.

--
Tim Young
Elevate Software
www.elevatesoft.com