Query Error - New to PHPRETS

[troydavisson]

Query Error - New to PHPRETS

[troydavisson]

Where you have an = (equal) sign in your query, change that to an =| (equal followed by a pipe). See if that works.

[raymondkennedy]

Appreciate the suggestion, that didn't fix the problem. Tried all variations of the query with your suggested change but same error still appears. I will keep at it and see if I can figure it out why. Any suggestions in the meantime, please feel free to comment, any help is greatly appreciated.

[albertcrowley]

I haven't had to touch my PHRETS code since I wrote one script a while ago
so this isn't expert advice: I had problems because I was setting various
constants, like the the second parameter to the SearchQuery where you are
using "RES", the way the examples had it. That didn't match the class name
that RETS database used, but I don't remember if it gave me an error or
just no results. After exploring my providers info in http://retsmd.com/ for
a bit I found all the specific constants that I needed for my queries.
Anyway, even if it doesn't help your particular problem, it might help get
a better understanding of the nature of the RETS data.

-Al

On Thu, Apr 11, 2013 at 9:16 PM, raymondkennedy [email protected]:

I am new to PHPRETS. I have been able to make a connection. I am just
starting to try and get a handle on this info. I tried using various
SearchQuery -> examples even those provided on here but I keep getting this
error. I can't figure out why.

Array ( [type] => rets [code] => 20203 [text] => Invalid Query Type. )

Here is my basic code...

$rets_login_url = "_";
$rets_username = "__";
$rets_password = "_*****";

require_once("phrets.php");

$rets = new phRETS;

$rets->AddHeader('Accept', "* / *");
$rets->AddHeader('RETS-Version',"RETS/1.7");
$rets->SetParam("debug_mode", true);

$connect = $rets->Connect($rets_login_url,$rets_username,$rets_password);

if ($connect)
{
echo " + Connected
\n";
} else {
echo " + Not connected:
\n";
print_r($rets->Error());
exit;
}

$search = $rets->SearchQuery("Property","RES,"(CIT=FRANKFORT)");

print_r($rets->Error());

I tried using listed names on examples sites like this one and looked up
the names with my MLS info. No matter what I put in there it gives me that
error.

Thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15
.

[freephile]

In the sample code you provided, you print out $rets->Error() in a block
that would occur without a successful connection. Are you sure that your
server supports version 1.7? I would also recommend using RetsMD to
visually inspect the Server objects and classes.

Greg Rundlett
founder / CEO
eQuality Technology
http://eQuality-Tech.com http://equality-tech.com/
voice 978-225-0471
[image: Twitter icon] http://twitter.com/eQualityTech
[image: Facebook icon] http://www.facebook.com/eQualityTechnology
[image: Google+
icon]http://plus.google.com/u/0/b/103166669544267620800/103166669544267620800
[image: LinkedIn icon] http://www.linkedin.com/company/3021433

On Thu, Apr 11, 2013 at 9:16 PM, raymondkennedy [email protected]:

I am new to PHPRETS. I have been able to make a connection. I am just
starting to try and get a handle on this info. I tried using various
SearchQuery -> examples even those provided on here but I keep getting this
error. I can't figure out why.

Array ( [type] => rets [code] => 20203 [text] => Invalid Query Type. )

Here is my basic code...

$rets_login_url = "_";
$rets_username = "__";
$rets_password = "_*****";

require_once("phrets.php");

$rets = new phRETS;

$rets->AddHeader('Accept', "* / *");
$rets->AddHeader('RETS-Version',"RETS/1.7");
$rets->SetParam("debug_mode", true);

$connect = $rets->Connect($rets_login_url,$rets_username,$rets_password);

if ($connect)
{
echo " + Connected
\n";
} else {
echo " + Not connected:
\n";
print_r($rets->Error());
exit;
}

$search = $rets->SearchQuery("Property","RES,"(CIT=FRANKFORT)");

print_r($rets->Error());

I tried using listed names on examples sites like this one and looked up
the names with my MLS info. No matter what I put in there it gives me that
error.

Thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15
.

[raymondkennedy]

Thanks everyone. RETSMD cleared everything up. My vendor sent me documentation that said our server supports 1.7 but RetsMD showed it as 1.5. In either case, it was a simple name change that fixed the error. Really glad to know about RetsMD, very helpful I am knew to this so as I proceed I will have plenty of questions, good to know there is a helpful group here.