SETRANGE does not apply

poppins

Hi everyone,

I have some troubles with the following piece of code:

MyRecord.RESET;

MyRecord.SETRANGE(DetailEvalTemp.Year,TempYear);

MESSSAGE('The selected year is = %1', TempYear);
MESSSAGE('So the year is = %1', DetailEvalTemp.Year);

The output is:

The selected year is = 2011
So the year is =

As you can see, SETRANGE does not apply :?

Where is the error??? What should I do???

mohana_cse06

What about

MyRecord.RESET;

MyRecord.SETRANGE(DetailEvalTemp.Year,TempYear);
IF MyRecord.FINDFIRST THEN;
MESSSAGE('The selected year is = %1', TempYear);
MESSSAGE('So the year is = %1', DetailEvalTemp.Year);

poppins

Infact, there was a little error:

MyRecord.SETRANGE(MyRecord.Year,TempYear);

and thank you, now it applies...

mohana_cse06

poppins wrote:

Infact, there was a little error:

MyRecord.SETRANGE(MyRecord.Year,TempYear);

and thank you, now it applies...

#-o

It is always prefered to use

MyRecord.SETRANGE(Year,TempYear);

DenSter

mohana_cse06 wrote:

It is always prefered to use

MyRecord.SETRANGE(Year,TempYear);

It really makes no difference, SETRANGE or SETFILTER both work properly as long as you know how to set the filterstring, there is no technical reason to use one over the other.

As it so happens, I like SETRANGE over SETFILTER too, but this 'preference' you talk about is purely our own personal preference.

mohana_cse06

DenSter wrote:

mohana_cse06 wrote:

It is always prefered to use

MyRecord.SETRANGE(Year,TempYear);

It really makes no difference, SETRANGE or SETFILTER both work properly as long as you know how to set the filterstring, there is no technical reason to use one over the other.

As it so happens, I like SETRANGE over SETFILTER too, but this 'preference' you talk about is purely our own personal preference.

Poppins and me didnt use SETFILTER word in our posts at all..
How did you think of that? :-k

The preference I am talking about is
MyRecord.SETRANGE(Year,TempYear);
MyRecord.SETRANGE(MyRecord.Year,TempYear);

DenSter

Again, this is YOUR personal preference, there is no technical reason to do it either way. There is nothing wrong with that code.

Although I also don't like the repetition, they both work exactly the same.

mohana_cse06

You also dont assume yourself which others didnt say...

DenSter

last word

mohana_cse06

DenSter wrote:

last word

:thumbsdown:

DenSter

mohana_cse06 wrote:

DenSter wrote:

last word

:thumbsdown:

Good one :thumbsup: