> The best will be to use the DDEX provider to get the Visual Studio=20 > Integration of the provider.
Yes - when I was answering your previous mail I realized this too.. However it doesn't work for me yet :-( > > > First - property FbDataReader.HasRows returns always true. > Oops - I hav= > e > > searched it up in the documentation just now and it says > that this prop= > erty > > simply is always true.. Ehm - why should we have such property then? > > According to my knowledge, there is no way how to determine > whether exe= > cuted > > query has returned some rows and (if yes) how many rows it > has returned= > .. > > ..Am i wrong? > No, and this is as designed. I have not used ADO with other databases - so I have a question to this.. This "always-true feature" was designed in the .NET Framework and e.g. SqlDataReader.HasRows works the same (strange) way or this is FBProvider specific behaviour (even though it is considered as "not bug")? I simply do not understand why the property even exists if it does nothing.. Maybe that other users do not understand this too - adding more info to documentation would stop all questions on this.. > > Second - we are using firebird databases with Unicode charset - i.e. > > rdb$bytes_per_character is set to value 3. > > We have following problem with the provider - sometimes it raises an > > IscException(335544321), even though there is (in my > opinion) no need f= > or > > throwing any exception. The same SQL statement that raises > this excepti= > on > > via FbProvider is succesfully executed via IB Expert. > IBExpert doesn't have proper UTF-8 support so it's not a valid test ;) Yes, I know about lack of support for UTF_8 in IBE.. It was irrelevent to write about testing in IBE to you, sorry for causing misunderstanding.. I only wanted to say this: 1) when I try to execute an update SQL statement (unfortunately this does not happen always) via FbProvider it throws an Exception 2) if I comment those few lines in XdrStream it is executed succesfully. And following select of updated data proves that the string was NOT trimmed or corrupted during executing the update. My conclusion is that the exception thrown in XdrStream is in "my" case useless and should not be thrown. I'll try to prepare test case for you.. Unfortunately I have to find out the statement that throws the exception when using the original XdrStream source code.. > Some questions here: > > 1. The Computer where you are trying to install the DDEX > provider where=20 > having Visual Studio 2005 betas ?? No > > 2 . Have you installed the Visual Studio SDK ( it's not th e:NET=20 > Framework SDK ) Yes. I am using VS Team Edition and VS SDK was installed from the original disc with VS2005.. > 3 . Have you modifed the machine.config file of .NET 2.0 > according to=20 > the changes proposed in the ReadmeDDEX.txt Yes > 4. Have you combined the .reg file that comes with the > provider into the=20 > Windows Registry with the %path% modified according to the changes=20 > proposed in ReadmeDDEX.txt ?? Yes :-( ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
