[libRETS-users] Login Issue

[Russ Perna]

My mistake, I had a typo in one of the field names I was calling.

Thanks for the help,
Russ
 
 

-----Original Message-----
From: librets-users-bounces at crt.realtors.org
[mailto:librets-users-bounces at crt.realtors.org] On Behalf Of Russ Perna
Sent: Friday, January 12, 2007 7:48 PM
To: 'For discussion and help for and by the users of the libRETS C++library'
Subject: RE: [libRETS-users] Login Issue


Keith,

When I set Standard Names to false, I get this error message:
Could not get URL [
http://rets15.raprets.com:6103/Westchester/WCTY/search.aspx: 403 

Any thoughts?

Thanks,
Russ
 

-----Original Message-----
From: librets-users-bounces at crt.realtors.org
[mailto:librets-users-bounces at crt.realtors.org] On Behalf Of Keith T. Garner
Sent: Friday, January 12, 2007 6:08 PM
To: For discussion and help for and by the users of the libRETS C++ library
Subject: Re: [libRETS-users] Login Issue


On Fri, 12 Jan 2007 4:35 pm, Russ Perna wrote:
> Thanks for getting back to me. I am using C# to access libRets.

Thanks.  Its good for us to know which are the active bindings that we're
supporting.

> I have another question if you don't mind me using the same thread. 
> When
> running this query:
> SearchRequest searchRequest = session.CreateSearchRequest("Property",
> "ResidentialProperty", "(MLNumber=2629826+)");
>
> I am getting the error message:
> Unauthorized query. The query could not be executed because supplied 
> login does not have access to the MLNumber field.

That error message is being generated by the RETS Server and just passed
along by libRETS.  I have to asume it speaks the truth.

> I was able to query by MLNumber in ezRets by using "MLNumber > 
> 2629826". Am I forming it wrong when using C#?

The query you sited above is exactly what ezRETS would generate given the
where clause you list here.

You might want turn on the http logging (and/or the error logging) in ezRETS
to see exactly what query your SQL is being turned into and use the http
logging in libRETS to see what its doing with your query.

Honestly, doing the translation in my head, they are the exact same query.
I'm not sure what the difference might be.

Okay, I just lied, I had some insight.  Here's what could be the source of
the problem:

SearchRequest has StandardNames defaulted to true.  I bet MLNumber isn't the
values when you have StandardNames on.  If you explicitly SetStandardNames
to false, you might see some succes.

Keith

--
Keith T. Garner                   kgarner at realtors.org
Managing Director - Center for REALTOR Technology National Association of
REALTORS (From his mobile device)
_______________________________________________
libRETS-users mailing list
libRETS-users at crt.realtors.org
http://mail.crt.realtors.org/mailman/listinfo/librets-users


_______________________________________________
libRETS-users mailing list
libRETS-users at crt.realtors.org
http://mail.crt.realtors.org/mailman/listinfo/librets-users