From: | "Joel Fradkin" <jfradkin(at)wazagua(dot)com> |
---|---|
To: | "'Joel Fradkin'" <jfradkin(at)wazagua(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Urgent! RE: E_Failed issue (also problem reading the record to edit it). |
Date: | 2005-08-31 17:41:20 |
Message-ID: | 000701c5ae53$335f7660$797ba8c0@jfradkin |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
I kind of got it to work using a larger number in
MaxLongVarcharSize=8190;
Modified to use
MaxLongVarcharSize= 132560;
But now other sql statement are returning E_failed.
I do not understand what this is setting and how it relates to the size of
text fields, can someone help me out here?
Joel Fradkin
-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Joel Fradkin
Sent: Wednesday, August 31, 2005 10:40 AM
To: pgsql-odbc(at)postgresql(dot)org
Subject: [ODBC] E_Failed issue (also problem reading the record to edit it).
My connection string is:
"DRIVER={PostgreSQL};DATABASE=wazagua;SERVER=192.168.123.121;PORT=5432;UID=p
ostgres;PWD=1brain;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=0;Ro
wVersioning=0;ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;Unknown
Sizes=0;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debug=0;CommLog=0;Optimiz
er=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;Bo
olsAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;LFConversio
n=1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVa
rBinary=0;UseServerSidePrepare=0"
Recently we have a client who can not see data they have entered.
It is still in the data base, but something has to be happening.
I did capture a log (I can re-create the issue).
The data not coming up is a text field. I have tested adding large text
amounts in the field and was able to retrieve them ok, so I am confused what
may be causing the problem (spent like 6 hours thus far with no solution). I
can display the field in our print preview (only difference is it has the
field by name.
I tried adding all the fields by name rather then a * but that did not help
the edit screen. Both use the same connection (asp page using the connection
above).
After testing I managed to make so my select screen no longer displays but
only has:
Error Type:
Microsoft Cursor Engine (0x80004005)
Data provider or other service returned an E_FAIL status.
/wazagua/app/searchlist.asp, line 1251
Which is an execute of
select * from viwcaselist where clientnum = 'FARM' And isdeleted=false and
CaseNum ilike '%00025%' Order BY OpenDate Desc,CaseNum limit 51
the field giving me the issue is in this select (was not blowing it up
before I messed around testing the data itself).
From the log the field in question has:
**** PGAPI_GetData: icol = 26, fCType = -8, field_type = 25, value = 'NOTE:
', cbValueMax=0
[SQLGetData]PGAPI_GetData: enter, stmt=24425856
num_rows = 51
I am not listing the contents as they are confidential but it is like 16k
long.
Any ideas are much appreciated
Joel Fradkin
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2005-08-31 17:52:45 | Re: Unicode support |
Previous Message | Cleber Nardelli | 2005-08-31 17:04:41 | Re: Transactions and SavePoints |