MS ODBC encoding issue
Sam Hu
samhudotsamhu at gmail.com
Sun Dec 23 23:18:51 PST 2012
On Friday, 21 December 2012 at 15:20:39 UTC, Regan Heath wrote:
> On Wed, 19 Dec 2012 06:33:16 -0000, Sam Hu
> <samhudotsamhu at gmail.com> wrote:
>
>> On Monday, 10 December 2012 at 14:43:08 UTC, Regan Heath wrote:
>>> >
>>> 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.
>>>>
>>> R
>>
>> I have such extra lib files to link successfully but I don't
>> find any way to upload here.Sorry.
>
> NP, I am up and running. I can run the test app and see my
> existing rows, plus insert new ones. I got it working with a
> connection string directly to an access database file on disk
> without needing a DSN, not sure why you were having trouble
> with that.
>
> So, what sort of data do I need to add, which will cause the
> issues you were originally having :)
>
> R
Really excited to hear that! As I said,field contains Chinese
characters will produce error during read from and write back to
database file; and can't work out a DSNless connection function.
Would be much appreciated if you would like to share your
complete code here.
More information about the Digitalmars-d-learn
mailing list