I don't think I described the problem sufficiently.
I'm getting the cursor back in VFP, but I believe the values are double
byte length. (Or something.)
I'm seeing the value of "c l o n g t e x t" in my cursor's column_name
column instead of what I was expecting as "clongtext". That's not just
a space in there that could be fixed with a replace all column_name with
strtran(column_name, " ", ""). I think I need to force the response to
be win-1252, or to post-process the cursor to be win-1252.
I'm trying to Google Rick Strahl's articles to see if he has a solution,
but my Google skills are lacking today.
Thanks Mike!
On 06/18/2012 02:53 PM, MB Software Solutions, LLC wrote:
> On 6/18/2012 2:26 PM, Kevin Cully wrote:
>> Hello Profoxians,
>>
>> I'm issuing a:
>> select * from information_schema.columns where table_name = '{mytablename}';
>> on a PostgreSQL 9.1 database. I believe I'm getting back UTF-8 values
>> in the VFP cursor field of "column_name".
>>
>> I'm drawing a blank on how to get this back to the format to be consumed
>> in VFP. Win-1252? Any tips? I should know this but ... it's moving
>> off into the fog of my memory. TIA.
> Not sure I completely understand, but a WAG:
>
> ? sqlexec(giHandle,'describe MyTable','curStructure')
>
>
>
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
