> Date: Mon, 23 Mar 2009 23:48:26 +0100
> From: Jiri Cincura <[email protected]>
> Subject: Re: [Firebird-net-provider] PlatformNotSupportedException
> To: "For users and developers of the Firebird .NET providers"
> <[email protected]>
> Message-ID:
> <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Mon, Mar 23, 2009 at 23:06, E.D. Epperson
> <[email protected]> wrote:
> > So first question, are my connection strings correct for the compact
> > edition?
>
> It's not correct at all. Why to use iso-8859-1? Everything in
> .NET is
> unicode. Hence if you're not creating some special purpose app it
> doesn't make sense.
>
> > Second question, is this a bug?? any idea how to fix it?
>
> No it's not bug. Simply on this device with CF the iso-8859-1
> isn't supported.
>
> --
> Jiri {x2} Cincura (CTO x2develop.com)
> http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
>
Ok, I changed the Charset in the connection string to UNICODE_FSS. At this
point the select statements are working correctly. But here is a question I
have...
The server is 2.1.1.17910, but the database was created several years ago and
used a charset of ISO8859_1. Can a Unicode client successfully read / write on
a db that has a default of IS)8859_1?
Do I need to rebuild the db? If so, How do you do that?
E. D. Epperson Jr.
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
