FINDFIRST & SETCURRENTKEY

Remco

Do you still need to use SETCURRENTKEY with the FINDFIRST, FINDLAST and FINDSET statement?

markborges

Which version of Navision supports these statements?

Waldo

On Native: always use it (ISAM)
On SQL: use SETCURRENTKEY to retrieve the recordset in an ordered way. SQL doesn't use it to fetch the data.

Mbad

Yes and 4.0 SP2+

kriki

Remco wrote:

Do you still need to use SETCURRENTKEY with the FINDFIRST, FINDLAST and FINDSET statement?

Depends in which order you want the records.
On SQL, it serves ONLY to define the order.
On Navision it serves to select the correct key for performance (and also ordering).

Waldo

so I was right?

kriki

Waldo wrote:

so I was right?

Yes, I just refrased it

Remco

So, does this mean that with using a FINDFIRST in a batchproces it is of no use to add a SETCURRENTKEY to make this batchproces faster.

kine

You can hint SQL server through SETCURRENTKEY (for example, he can change the execution schema when SQL knows that you want to order the set in some way...).