[ezRETS-users] Bug?

[Keith T. Garner]

On 5/4/07 2:02 PM, Jack Burnish wrote:
> I'm not sure if this is a bug or not.

Yep, this is a known bug.  If you turn on the "Treat Decimal as Varchar"
you'll get the value.  Unfortunately, not as a decimal, but you'll get it.
Then in your language of choice you can cast it as nessessary.

> However, I'm running into an issue where Net 2.0 can't translate the
> Decimal field correctly.  This isn't an error with EZRets, just a
> compatibility issue with .aspx files.  Excel happily renders the decimal
> field with no problem.

Excel and .NET (well, the ADO driver) actually ask for the decimal in two
different ways.  I'm trying to figure out why the one way doesn't work, but
it some low level code I *thought* I was doing right, but its a known bug
that its wrong.  I've got some more coding to do on it, but with mid-year
coming up, I'm slightly distracted.

> On another note, I noticed a ticket that said 'cannot edit query in
> wizard' for Excel.  This is absolutely correct.  HOWEVER, you can open
> MSQuery, and edit the SQL graphically, rather than by hand.

That's an error message from excel and not actually something in ezRETS.
I'm trying to figure out why it thinks it can't edit it, but that's a
different matter.

I really need to write a FAQ (or find a volunteer to do so.)

> This is
> currently what I'm testing my SQL against before using it in VS 2005,
> creating the SQL with MS Query in Excel 2003, then cutting and pasting
> the resulting SQL into VS 2005, where it promptly tells me to go away
> due to the decimal fields translating oddly.

If you're working in Visual Studio, you might want to look at the .NET
interface to libRETS.  Then you can code directly to RETS (and get some more
info out of the metadata) then through the limited filter of ODBC.

Keith

-- 
  Keith T. Garner - Managing Director - Center for REALTOR® Technology
   kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt