Re: figuring out why I am having this issue

That is the error description
If con.Errors.Count >= 1 Then
set Error = con.Errors.Item(0)
'take the error code from SQL Server
ErrCode = Error.NativeError
response.Write(cstr(Error.Description))
Response.End
End If

Could be there is better method, but this what I have been using.
I have tested putting a 300 meg text field in the data base nad it worked so
not clear why it works on most data and this one does not.
I did email you the log file (not sure it is any help).

Joel Fradkin

Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305

jfradkin(at)wazagua(dot)com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.

-----Original Message-----
From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
Sent: Thursday, September 01, 2005 11:07 AM
To: Joel Fradkin
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] figuring out why I am having this issue

> -----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