SETRANGE over SETFILTER

mickuk · 2006-03-19

Hi All,

Is there any main benefit of using Record.SETRANGE(Field [,FromValue] [.ToValue]) over Record.SETFILTER(Field, String, [Value],...)? Would one be correct to assume that SETRANGE() limits your result set to the requested range....for example:

say you have the following records

Entry No. Name
1 Big Bill
2 Roger Hill
3 Badger Pill
4 Nigel Will

If you said SETRANGE("Entry No.", '1', '3') would the effects be a record set that is shown below?

Entry No. Name
1 Big Bill
2 Roger Hill
3 Badger Pill

I presume that the SETFILTER option just applies a filter thus sorting the records that you would have returned from running the function? Probably something that has been mentioned before, however my searches have not been very productive. I have read what is detailed in the "Navision Financials Help" and the functions are described to be very similar. Some clarification as to which is the most productive would be appreciated.

Thanks in advance!

Wolfikas · 2006-03-19

Hi,
SETRANGE can be used for simple filters, for example:

Cust.SETRAGE("No.",'5000');

- only one number;

Cust.SETRAGE("No.",'5000'..'6000');

- all numbers from 5000 to 6000.

SETFILTER is used for more complex filters like:

Cust.SETFILTER("No.",'%1|%2','5000','6000');

- number 5000 or number 6000;

Cust.SETFILTER("No.",'<>%1&<%2','5000','6000');

- all numbers less than 6000, except 5000.

Savatage · 2006-03-19

http://www.mibuso.com/forum/viewtopic.php?t=6925

ara3n · 2006-03-19

Wolfikas wrote:
Cust.SETRAGE("No.",'5000'..'6000');
- all numbers from 5000 to 6000.

This should be

Cust.SETRANGE("No.",'5000','6000');

Rule of thumb is to allways use SETRANGE, Unless you need to write complex filters.

SETRANGE over SETFILTER

Comments

Categories