> You can still add new records. The 'problem' may be seeing
> the new ones after a refresh. On a slow connection, the plan
> should always be - only access the records you NEED.

This is exactly what I want. In fact navigation is not a must for this
screen and I don't have any grid on it. The main goal is to provide a fast
way to enter records (I think I had accomplished this) and a fast way to
locate and modify any record on the database.

> See note above. All you are doing is moving when the client
> looks for and downloads records that they may not even need.
> If you scroll down the whole list, all the records then get
> transfered - but as you scroll.

OK this is what I want. I doesn't matter if it takes a litle ms per record,
but it was no good at all to have to way for 6 or 10 seconds just to load
the whole table. :(

> >>#2: Use POS attribute of OrderingLinks property (horizontal dataset
> >>partitioning)
> >>
> >
> > Sorry. I can't imagine how to do that and I can't find additional
> > information.
>
> It is a little difficult to find ( any Tech Sheet on this
> Helen ? ). Again though, it is just reducing the amount of
> data that is accessed in a query. You may need to think
> about providing a search facility on the client, and only
> handling a sub-set of the records that way.

In fact on the query I just want to return a record to be edited but I have
to be able to searche it in two ways: human readable way (two fiels both
indexed) and id (LongInt identifier).


---
Toni