Re: psqlODBC text length with no records
От | Adrian Klaver |
---|---|
Тема | Re: psqlODBC text length with no records |
Дата | |
Msg-id | 53739759.1040303@aklaver.com обсуждение исходный текст |
Ответ на | psqlODBC text length with no records (Barry Bell <Barry.Bell@hartehanks.com>) |
Ответы |
Re: psqlODBC text length with no records
|
Список | pgsql-odbc |
On 05/14/2014 09:08 AM, Barry Bell wrote: > None of the below information helps because we are taking the output cursor > From the postgrest sql, putting it into a VFP grid and displaying to the user. > > With theB0(Max varchar)=254 setting, Postgres for lengths 1-254 returns a "char" > In vfp, when displayed to the user in a grid, the value of field is shown > > With theB0(Max varchar)=254 setting, Postgres for lengths=0 or null returns a "Memo" > In vfp, when displayed to the user in a grid, "Memo" is shown in the field instead of the value > > With theB0(Max varchar)=254 setting, Postgres for length over 256 returns a "Memo" > In vfp, when displayed to the user in a grid, "Memo" is shown in the field instead of the value > We only have some code after the sql that sorts the cursor and VFP is unable to sort on the MEMO fields. > > Our issue is when Postgres is returning a fireld with 0 or null length, > The driver is not using the B0(Max varchar) setting. Well you could always try Parse Statements: http://psqlodbc.projects.pgfoundry.org/docs/config.html > > Barry Bell > Senior Developer/Analyst -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-odbc по дате отправления: