> One questions remains, though.
> If ISO8859_1 is not suitable for that purpose, why have I never been
> noticing this before? I mean, why do the other drivers/providers
> translate those bytes correctly to a Euro sign?
ISO 8859-1 and WIN-1252 are almost exactly the same, except that where ISO
88
On 7/11/07, Carlos Guzmán Álvarez <[EMAIL PROTECTED]> wrote:
> "Whatever you are trying to achieve here, note that there is no euro-
> character in ISO-8859-1. You can use ISO-8859-15, WIN1252, UTF8
> or even more strange options, but not ISO-8859-1."
Nice! I know only Win1250 (or iso-8859-2), wh
Error building Provider for Mono
Key: DNET-104
URL: http://tracker.firebirdsql.org/browse/DNET-104
Project: .NET Data provider
Issue Type: Bug
Components: ADO.NET Provider
Affects Versions: 2.5.
Ok,
I configures a Windows sandox with Mono 1.2.4 and Nant.
But the provider is not created!! - Log file is attached.
Thanks in advance
Eduardo
""Carlos Guzmán Álvarez"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hello:
I am trying to build the provider in Linux/MONO using:
More information:
although the error says that type information could not be retrieved,
there IS type information!
If I created an empty dataset and then go to dataset designer, I can
view the tables and fields and their properties. The properties tell the
correct lenght and fieldtype for each
Hi Stephen,
seems I finally got it to work, although I'm quite sure I did those
steps before.
Just the two additional question from my original posting remain open:
1. What are the purposes/differences of
FirebirdDDEXProviderPackageLess32.reg and FirebirdDDEXProvider32.reg?
2. If I use DDEX Pr
Hi,
after getting the DDEX provider to work, at least I thought so, I can
view the schema information of my database.
But when I try to create a dataset, I get the error "Could not get type
information for '...'" (...= my table name).
Ideas, anyone?
Thanks,
Mathias Wuehrmann
Germany
---
Thanks for the answer, Carlos.
So, I should use Win1252 and be well? That's not too big a problem.
I have about 300 tables, but most of the objects do not override the
database's charset. Can I change the database's charset by restoring
a backed up db into an (empty) database with another charset?
Now you got me, Jiri :)
I have once and never again used ISQL when I started converting DBF to
Firebird 4 years ago. If I need to use it to make further tests, I
will get the documents and use it.
Carlos' Answer might be helping out as well, thanks.
~~~Ihre Nachricht~~~
JC> It's definetely enc
Hello:
> I am a bit puzzled about a problem which came quite unexpected to me.
> It seems that I cannot get our Euro-sign (ALT+0128) through to the
> client GUI via the .net Provider.
I'm going to reproduce here an answer of Peter Jacobi on this topic some
time ago:
"Whatever you are trying to
It's definetely encoding problem. It looks like, that the sign isn't
added into DB right.
When you connect using isql with proper encoding (probably DOS852) did
you get the sign right?
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
---
> Damn, I missed, that you're not inserting (but the connection string
> should be changed at all). What exception you get?
No problem, because for the nearest future I definitely do plan to
insert data via the (new) .net application. I am doing the latest
tests and now stumbled over that curiosit
Hi Carlos,
Carlos Guzmán Álvarez schrieb:
> This is wrong version should be 2.0.0.0
also tried 2.0.0.0 - no success.
Regards,
Mathias Wuehrmann
Germany
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C
On 7/11/07, André Knappstein, Controlling <[EMAIL PROTECTED]> wrote:
> But the data was mostly not entered via my .net-application.
Damn, I missed, that you're not inserting (but the connection string
should be changed at all). What exception you get?
--
Jiri {x2} Cincura (Microsoft Student Part
> You should use unicode (UTF8) in connection string, on 99% you're
> putting data from .NET in Unicode.
Thanks, Jiri.
I will give that a try this afternoon.
But the data was mostly not entered via my .net-application.
-
T
On 7/11/07, André Knappstein, Controlling <[EMAIL PROTECTED]> wrote:
> Charset of Connection is ISO8859_1
You should use unicode (UTF8) in connection string, on 99% you're
putting data from .NET in Unicode.
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://w
Hello Gang,
I am a bit puzzled about a problem which came quite unexpected to me.
It seems that I cannot get our Euro-sign (ALT+0128) through to the
client GUI via the .net Provider.
Database standard for character type fields is ISO8859_1,
Database-fields are ISO8859_1,
Charset of Connection is
Hello:
>
>
> type="System.Data.Common.DbProviderConfigurationHandler, System.Data,
> Version=2.1.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
This is wrong version should be 2.0.0.0
-
This SF.net email i
Hello:
> I am trying to build the provider in Linux/MONO using:
>
> make –f makefile
>
> Inside the build\linux directory, but I am getting the error
> makefile:36: *** multiple target patterns. Stop.
>
> Can anyone give a hand with this?
It could be broken as there are too m
19 matches
Mail list logo
