Re: figuring out why I am having this issue
От | Dave Page |
---|---|
Тема | Re: figuring out why I am having this issue |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9DFD@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | figuring out why I am having this issue ("Joel Fradkin" <jfradkin@wazagua.com>) |
Список | pgsql-odbc |
> -----Original Message----- > From: Joel Fradkin [mailto:jfradkin@wazagua.com] > Sent: 01 September 2005 16:00 > To: Dave Page > Cc: pgsql-odbc@postgresql.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
В списке pgsql-odbc по дате отправления: