I have a scenario where for a certain Table,

(1) print the primary key of record p.

(2) do some stuff, scrolling through Table, but no edits, inserts, deletes,

(3) Table.RecNo := p;

(4) print value of primary key.

Printed keys in (1) and (4) are different. The value from (1) is definitely
correct, from (4) not so much.

Before I start investigating: Is (3) supposed to work correctly at all
times, or only under specific circumstances?

RJ

Roy,

<< Before I start investigating: Is (3) supposed to work correctly at all
times, or only under specific circumstances? >>

Do you have a range active ?

--
Tim Young
Elevate Software
www.elevatesoft.com

No range, but this is a detail table.

RJ

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:09E2F761-1844-4509-AC07-DFAC45A4B559@news.elevatesoft.com...
> Roy,
>
> << Before I start investigating: Is (3) supposed to work correctly at all
> times, or only under specific circumstances? >>
>
> Do you have a range active ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Roy,

<< No range, but this is a detail table. >>

If by "detail" you mean detail for a master-detail link, then yes, it's got
a range on it.

--
Tim Young
Elevate Software
www.elevatesoft.com

And then RecNo cannot be assigned to?

Let me add some more info, as my original question was quite general: the db
contains maybe 20-25 master records, each with some 1000 records in this
particular detail table. If a range would be causing the problem, I would
expect the RecNo to be off by possibly a lot, but what we see is after (say)
RecNo := 900, the table involved is really on record 902. Just off, and
always 'forward'. Let me try to email you a little sample project after
Christmas. Happy Holidays!

RJ

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:1157E87B-1C9D-4E7E-B9D7-28DDC5A97F30@news.elevatesoft.com...
> Roy,
>
> << No range, but this is a detail table. >>
>
> If by "detail" you mean detail for a master-detail link, then yes, it's
> got a range on it.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Roy,

<< And then RecNo cannot be assigned to? >>

No, not at all.  It's the same issue that you already reported for 1.06 with
respect to setting the RecNo property with ranges.  It will be fixed in
1.07.

<< Let me add some more info, as my original question was quite general: the
db contains maybe 20-25 master records, each with some 1000 records in this
particular detail table. If a range would be causing the problem, I would
expect the RecNo to be off by possibly a lot, but what we see is after
(say) RecNo := 900, the table involved is really on record 902. Just off,
and always 'forward'. >>

That's just the way the bug manifests itself.  I'd really have to go into a
lot of detail to explain why, but this buggy behavior is "normal" given the
way that the functionality works in the engine.

<< Let me try to email you a little sample project after Christmas. Happy
Holidays! >>

Thanks, but it isn't necessary since it has already been fixed.

--
Tim Young
Elevate Software
www.elevatesoft.com