From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Joel Fradkin" <jfradkin(at)wazagua(dot)com> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: figuring out why I am having this issue |
Date: | 2005-09-01 15:07:24 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9DFD@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Joel Fradkin [mailto:jfradkin(at)wazagua(dot)com]
> Sent: 01 September 2005 16:00
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] figuring out why I am having this issue
>
> I don't get that kind of control.
>
> In asp you assign a record set:
> set rec = cmd.Execute
>
> Rec is not defined other then
> set rec = server.CreateObject("ADODB.Recordset")
Yeah, I know - I think you miss my point though. If for some reason the
DB doesn't tell us the size of the column (because it's a text field for
example), we default to max_lvc. If the data is longer than that though,
ADO might overflow an allocated buffer. I would hope Microsoft wrote it
better than than, but it's the best I've got right now!!
> What is weird is one SQL from this record where works and
> another does not.
Which kinda throws the size issue out the window. You sure this is
caused by ODBC? Can't ASP be more verbose than E_FAILED?
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Fradkin | 2005-09-01 15:15:54 | Re: figuring out why I am having this issue |
Previous Message | Joel Fradkin | 2005-09-01 14:59:58 | Re: figuring out why I am having this issue |