Thanks Troy,
That works but is there no way to use friendly names for the query
fields? I noticed that when I pass the option array* into the
SearchQuery method if I leave out "Format" => "COMPACT" I'll get my
results with friendly value names, like "Pittsfield" and not
"OY40LJN515S". What's the benefit of using COMPACT vs whatever other
possible values are specified?
I'm sure I could figure this out but if you or someone already knows
it would save me some time...is there a function that will look up the
friendly name and return the value so I can use it in user-driven
queries? This would be a great addition to phrets.
*Where is the option array explained? I've been looking everywhere
and can't find it. Also, an observation: FLEXMLS doesn't seem to
recognize the StandardNames option flag and returns an empty resource.
> Check outwww.retsmd.comusing the access details you have. Once you're there, pull up A - Residential and find the LIST_15 field (LIST_105 is MLS#). To the right will be a 'Values' link. Click that and you'll see the possible values of that field. Your query needs the far left value.
>
> So:
>
> (LIST_15=|STRINGOFCHARS)
>
> Each property type has their own code for Active so get the others as needed.
>
> The pipe operator designates a OR condition on a lookup field. I started a DMQL tutorial but haven't gotten back to finish yet so maybe I can do that this next week. In the meantime, page 56ish of the RETS 1.7.2 spec (on
rets.org) outlines the syntax.
>
> HTH,
>
> Troy
>