MS ODBC encoding issue
Regan Heath
regan at netmail.co.nz
Mon Dec 10 06:43:07 PST 2012
On Fri, 07 Dec 2012 00:27:57 -0000, Sam Hu <samhudotsamhu at gmail.com> wrote:
> On Thursday, 6 December 2012 at 16:44:01 UTC, Regan Heath wrote:
>> On Thu, 06 Dec 2012 01:26:32 -0000, Sam Hu <samhudotsamhu at gmail.com>
>> wrote:
>>> Known issues:
>>>
>>> Under console reading Access table recordsets works fine ,inserting a
>>> new record which contains only English characters works fine as
>>> well,but inserting new record which contains Chinese character will
>>> crash;
>>>
>>> If calling the fetchAll in a DFL gui form and try to display the
>>> result value in a Text control,English values works fine but the Text
>>> control will display nothing when any record (row/field) contains
>>> Chinese character.
>>
>> Where do the win32.sql etc modules come from?
>>
>> R
>
> You can find it from below links:
> http://www.dsource.org/projects/bindings/wiki/WindowsApi
> https://github.com/AndrejMitrovic/WindowsAPI
Ahh, of course. Now I'm having linking issues :p
I'm using VisualD and I've added odbc32.lib to the right place, but some
symbols are still missing - specifically the W versions. I've dumped the
symbols in the DMC odbc32.lib and it's missing those symbols.
I am guessing I should be using converted M$ libs and I'll do this next,
when I get a spare moment (work has been busy lately).
R
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
More information about the Digitalmars-d-learn
mailing list