SETRANGE: Both values included. With SETFILTER it is possible to exclude the limits. My favorite SETFILTER: SETFILTER("Ending date", '%1|%2..', 0d, WORKDATE);
YOU FORGOT TO TELL THEM THAT SetRange ALSO IS MORE PERFORMANT THAN THE OTHER OPTIONS! But your points of using the power of type checking is of course correct.
So, are you, once and for all, as the product group official representitive here on RU-vid , stating that: The SQL SELECT statement created from SetRange is performing better than the SQL SELECT statement created from SetFilter?
@@Hougaard I am in no way in the authority to represent the product group. And I really hope we don't end up creating different SQL statements. But the runtime cost is cheaper since you don't have to parse the input text, does it matter in most cases? No, but let's find all arguments to steer people towards SetRange.
But if it only the parsing cost we're talking about, then that's less than the deviation of the latency of the subsequently SQL operation. The reason I didn't mention this in the video, is that there has been soo many urban legends surrounding this, going all the way back to Peter Bang.... Someone have talking with someone saying that setfilter is .... than setrange.
Dear Eric, How can we put the filter inside the filter pane?. for example onopen page put true inside filter pane for a boolean record, like saved view. Best Regards, NAV
@@Hougaard this will put the filter as background and we can not remove it. Anyway, I fix it by using the filtered record inside (settable view) function. Thanks for your reply dear. Nav
Can it be imaginable to substitute setrange and setfilter in the future? Wouldn't it be easier to have something like the where clauses in sql? This would avoid having x lines with setfilter and setrange.
