Menu
▾
▴
firebird-odbc-devel — All about development of Firebird ODBC driver donated by IBPhoenix
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(23) |
Sep
(6) |
Oct
(2) |
Nov
(2) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
(14) |
Mar
(16) |
Apr
(14) |
May
(25) |
Jun
(38) |
Jul
(22) |
Aug
(39) |
Sep
(3) |
Oct
(13) |
Nov
(47) |
Dec
(3) |
| 2003 |
Jan
(38) |
Feb
(39) |
Mar
(24) |
Apr
(57) |
May
(30) |
Jun
|
Jul
(39) |
Aug
(90) |
Sep
(41) |
Oct
(141) |
Nov
(158) |
Dec
(137) |
| 2004 |
Jan
(86) |
Feb
(169) |
Mar
(100) |
Apr
(83) |
May
(94) |
Jun
(77) |
Jul
(85) |
Aug
(54) |
Sep
(45) |
Oct
(36) |
Nov
(42) |
Dec
(70) |
| 2005 |
Jan
(46) |
Feb
(44) |
Mar
(50) |
Apr
(73) |
May
(90) |
Jun
(87) |
Jul
(41) |
Aug
(47) |
Sep
(28) |
Oct
(23) |
Nov
(44) |
Dec
(81) |
| 2006 |
Jan
(21) |
Feb
(9) |
Mar
(82) |
Apr
(14) |
May
(109) |
Jun
(175) |
Jul
(188) |
Aug
(44) |
Sep
(5) |
Oct
(47) |
Nov
(15) |
Dec
(34) |
| 2007 |
Jan
(75) |
Feb
(24) |
Mar
(30) |
Apr
(4) |
May
(28) |
Jun
(9) |
Jul
(13) |
Aug
(13) |
Sep
(29) |
Oct
(15) |
Nov
(19) |
Dec
(12) |
| 2008 |
Jan
(7) |
Feb
(19) |
Mar
(1) |
Apr
(7) |
May
(13) |
Jun
(19) |
Jul
(17) |
Aug
(29) |
Sep
(15) |
Oct
(37) |
Nov
(18) |
Dec
(29) |
| 2009 |
Jan
(23) |
Feb
(12) |
Mar
(8) |
Apr
(16) |
May
(11) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(9) |
Nov
(17) |
Dec
(31) |
| 2010 |
Jan
(15) |
Feb
(5) |
Mar
(4) |
Apr
(8) |
May
(1) |
Jun
(5) |
Jul
(17) |
Aug
(2) |
Sep
(12) |
Oct
(33) |
Nov
(14) |
Dec
(24) |
| 2011 |
Jan
(11) |
Feb
(2) |
Mar
(34) |
Apr
(11) |
May
(12) |
Jun
(3) |
Jul
(6) |
Aug
(11) |
Sep
(10) |
Oct
(1) |
Nov
(8) |
Dec
|
| 2012 |
Jan
(16) |
Feb
(2) |
Mar
|
Apr
(2) |
May
(6) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
|
Oct
(7) |
Nov
(22) |
Dec
(2) |
| 2013 |
Jan
(1) |
Feb
(24) |
Mar
(15) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(2) |
Aug
|
Sep
(2) |
Oct
(6) |
Nov
(10) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
(5) |
| 2015 |
Jan
(1) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2016 |
Jan
(1) |
Feb
(9) |
Mar
(4) |
Apr
|
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(13) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(12) |
Oct
(4) |
Nov
|
Dec
|
| 2018 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
(2) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Craig F. <cf...@po...> - 2013-09-18 21:06:35
|
Friends,
I have a database installed on a central computer (not running a server
OS) that I am trying to connect to two clients. The database folder is
shared on the network as L:\database\ All PC's are running Windows 7.
For one client simply connecting to L:\Database|{dbname} in the ODBC
configuration worked fine. For the other, I cannot connect no matter
what string I use. Following the Help documentation I have tried all
combinations suggested. But each time I cannot connect. Both client PC's
are running the same, newly updated 2.0.2.153 ODBC Driver. Any
suggestions?? Why did L:{etc} work when this not documented as a valid
connect string/method? Something hiding in the code we don't know about?
Any comments would be appreciated.
Craig
--
Craig Fogg
Phone 603-380-3208
Email cf...@po...
Tweet rebelfogg
|
|
From: Alexander P. <ale...@gm...> - 2013-07-25 12:36:43
|
Hi Jorge, This file (readme.txt) was not updated for a long time. All changes in ODBC driver are included into "changes-v20.log", but "changes-v20.log" is not included into Firebird ODBC driver Windows installer. I think that it is necessary to include changes-v20.log into windows installers too. Regards, Alexander On 24.07.2013 18:05, Jorge Andrés Brugger wrote: > Hi all. > > readme.txt says "All the new features and fixes are documented in the > release notes" ... But, where are the release notes? I´m particularly > interested in the "Improved installation (and uninstallation) routines > for Win32 and Linux". > > Thanks! > |
|
From: Jorge A. B. <li...@da...> - 2013-07-24 14:32:00
|
Hi all. readme.txt says "All the new features and fixes are documented in the release notes" ... But, where are the release notes? I´m particularly interested in the "Improved installation (and uninstallation) routines for Win32 and Linux". Thanks! -- Jorge Andrés Brugger Informática DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia Comodoro Rivadavia, Chubut, Argentina Teléfono (0297) 446-4444 int. 103 Correo electrónico: jbr...@da... Website: www.dasu.com.ar -- Antes de imprimir este mensaje, piense si es verdaderamente necesario hacerlo. |
|
From: Jorge A. B. <li...@da...> - 2013-05-29 19:31:01
|
Thanks Alexander! Firebird and Fireboird ODBC are moving in the right direction. Regards. El 28/05/2013 05:07 p.m., Alexander Potapchenko escribió: > Jorge, > > Of course I will rename the driver name to "Firebird ODBC driver" in new > versions, it is more correctly because the driver does not support last > versions of Interbase entirely. > BTW, there are freeware Embarcadero InterBase ODBC Driver - > http://cc.embarcadero.com/item/28975, it is based on Firebird ODBC driver. > > On 28.05.2013 22:09, Jorge Andrés Brugger wrote: >> Today I've faced a new problem: I´ve documented a connection string to a >> wiki, and "Driver=Firebird/InterBase(r) driver" gets transformed to >> "Driver=Firebird/InterBase® driver". I´ve copied such string to my app >> config, and took me several minutes until I´ve found the problem. I´ve >> checked the other odbc driver names I have on my PC, and none includes >> "special chars". Another reason to change the name ... :) >> It's fine if I create a suggestion on the tracker? >> >> Regards! >> > -- Jorge Andrés Brugger Informática DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia Comodoro Rivadavia, Chubut, Argentina Teléfono (0297) 446-4444 int. 103 Correo electrónico: jbr...@da... Website: www.dasu.com.ar |
|
From: Alexander P. <ale...@gm...> - 2013-05-28 20:07:49
|
Jorge, Of course I will rename the driver name to "Firebird ODBC driver" in new versions, it is more correctly because the driver does not support last versions of Interbase entirely. BTW, there are freeware Embarcadero InterBase ODBC Driver - http://cc.embarcadero.com/item/28975, it is based on Firebird ODBC driver. On 28.05.2013 22:09, Jorge Andrés Brugger wrote: > > Today I've faced a new problem: I´ve documented a connection string to a > wiki, and "Driver=Firebird/InterBase(r) driver" gets transformed to > "Driver=Firebird/InterBase® driver". I´ve copied such string to my app > config, and took me several minutes until I´ve found the problem. I´ve > checked the other odbc driver names I have on my PC, and none includes > "special chars". Another reason to change the name ... :) > It's fine if I create a suggestion on the tracker? > > Regards! > -- Alexander Potapchenko Team leader LASP Technologies, http://www.lasptech.ru |
|
From: Jorge A. B. <li...@da...> - 2013-05-28 18:37:39
|
El 12/04/2011 09:52 a.m., Alexander Potapchenko escribió:
> On 12.04.2011 15:54, Jorge Andrés Brugger wrote:
>> ODBC driver 2.0 is still compatible with Interbase? or should better be
>> renamed to "Firebird ODBC driver"?
>>
>> Regards!
>>
> I think that ODBC driver 2.0 is compatible with Interbase, but I didn't
> test the driver with IB.
> The Firebird/InterBase(r) driver is the historical name and I think that
> many application can use the such connection string:
> strConn = "driver={Firebird/InterBase(r) driver}; Database=;
> UID=SYSDBA;PWD=masterkey"
> Therefore I think that to rename the driver is the bad idea as yet.
>
> Regards,
> Alexander
Today I've faced a new problem: I´ve documented a connection string to a
wiki, and "Driver=Firebird/InterBase(r) driver" gets transformed to
"Driver=Firebird/InterBase® driver". I´ve copied such string to my app
config, and took me several minutes until I´ve found the problem. I´ve
checked the other odbc driver names I have on my PC, and none includes
"special chars". Another reason to change the name ... :)
It's fine if I create a suggestion on the tracker?
Regards!
--
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar
|
|
From: Daniel V. <da...@vo...> - 2013-04-10 20:08:17
|
Hi,
when using the Firebird ODBC driver with unixODBC, the Wide-Functions
like SQLExecDirectW fails.
UnixODBC defines SQLWCHAR as a 2-Byte value. I've transformed my
wchar_t* strings to UCS2 and call SQLExecDirectW() with them.
Here is the trace (debug version):
----
SQLExecDirectW
Preparing statement:
INSERT INTO FOO VALUES(NU
Preparing statement:
INSERT INTO FOO VALUES(NU
HY000:1:-104:[ODBC Firebird Driver][Firebird]Dynamic SQL Error
SQL error code = -104
Unexpected end of command - line 1, column 24
----
It seems that something in the ODBC driver truncates the
statement to the half. A short look into the code shows this function
inside the ConvertingString template (MainUnicode.cpp):
SQLCHAR * convUnicodeToString( SQLWCHAR *wcString, int length )
{
size_t bytesNeeded;
wchar_t *ptEndWC = NULL;
wchar_t saveWC;
if ( length == SQL_NTS )
length = (int)wcslen( (const wchar_t*)wcString );
...
I think the problem is that wcslen() expects a whar_t (4 bytes) sequence,
while SQLWCHAR is 2 bytes long.
Because I'm unsure if my code is correct, I've tested the same with
python3 and pyodbc (which uses the wide-functions, too).
This results in the same issue, so using the firebird odbc driver
with pyodbc/python3 is impossible for the moment.
Could anyone confirm this issue?
--
Daniel Vogelbacher
www.chaospixel.com
cytrinox@freenode/ircnet/quakenet
|
|
From: Daniel V. <da...@vo...> - 2013-04-10 20:07:20
|
Hi,
when using the Firebird ODBC driver with unixODBC, the Wide-Functions
like SQLExecDirectW fails.
UnixODBC defines SQLWCHAR as a 2-Byte value. I've transformed my
wchar_t* strings to UCS2 and call SQLExecDirectW() with them.
Here is the trace (debug version):
----
SQLExecDirectW
Preparing statement:
INSERT INTO FOO VALUES(NU
Preparing statement:
INSERT INTO FOO VALUES(NU
HY000:1:-104:[ODBC Firebird Driver][Firebird]Dynamic SQL Error
SQL error code = -104
Unexpected end of command - line 1, column 24
----
It seems that something in the ODBC driver truncates the
statement to the half. A short look into the code shows this function
inside the ConvertingString template (MainUnicode.cpp):
SQLCHAR * convUnicodeToString( SQLWCHAR *wcString, int length )
{
size_t bytesNeeded;
wchar_t *ptEndWC = NULL;
wchar_t saveWC;
if ( length == SQL_NTS )
length = (int)wcslen( (const wchar_t*)wcString );
...
I think the problem is that wcslen() expects a whar_t (4 bytes) sequence,
while SQLWCHAR is 2 bytes long.
Because I'm unsure if my code is correct, I've tested the same with
python3 and pyodbc (which uses the wide-functions, too).
This results in the same issue, so using the firebird odbc driver
with pyodbc/python3 is impossible for the moment.
Could anyone confirm this issue?
--
Daniel Vogelbacher
www.chaospixel.com
cytrinox@freenode/ircnet/quakenet
|
|
From: Alexander P. <ale...@gm...> - 2013-03-22 13:04:46
|
On 22.03.2013 16:52, André Knappstein wrote: > houh, hough, hough... brrrr. > > please accept my apologies for stealing your time. > > I remembered that I can also make a "trace" of ODBC calls, something > that Mr. Tsvigun once used to find and eliminate a problem in > the driver (around 2004). > While trying to create the trace I saw that, for whatever reason I'll > never understand, I had installed an outdated ODBC driver on this > machine. > Re-Installing .152, all seems to work fine. Please excuse me for the > trouble. André, Yes, MS Word 2007 works fine with odbc driver 152. > Will you come to Luxemburg this year? There are so many guys > here I am owing a round of best czech or belgian beer for all the > time I'm stealing from them, one more won't matter :-) > No, I will not come to Luxemburg this year unfortunately :-) Regards, Alexander -- Alexander Potapchenko Team leader LASP Technologies, http://www.lasptech.ru |
|
From: André K. <Kna...@be...> - 2013-03-22 12:50:20
|
houh, hough, hough... brrrr. please accept my apologies for stealing your time. I remembered that I can also make a "trace" of ODBC calls, something that Mr. Tsvigun once used to find and eliminate a problem in the driver (around 2004). While trying to create the trace I saw that, for whatever reason I'll never understand, I had installed an outdated ODBC driver on this machine. Re-Installing .152, all seems to work fine. Please excuse me for the trouble. Will you come to Luxemburg this year? There are so many guys here I am owing a round of best czech or belgian beer for all the time I'm stealing from them, one more won't matter :-) > Hi, > Tell in-depth information how to reproduce your problem please. > On 20.03.2013 17:28, André Knappstein wrote: >> Hi Gang! >> >> Is there a known technical reason why I can open literally any ODBC >> driven data source in MS Word (2007 and higher), but *not* Firebird? >> >> Do I have to make any settings which escaped me so far, or will it >> just not work or is the problem widely unknown so far? I'd like to >> prepare some views in Firebird and make them available for some >> assistants (creating mail merges). >> >> There is no problem in MS Excel (via MSQuery), but using the same >> *.dqy throws "unable to connect to datasource: library 'C:\program >> files\Firebi' failed to load", with an additional information >> "SQL-Status 08004, return code: SQL_ERROR". >> >> Creating a new connection throws "Unable to retrieve table metadata" >> (original in German: "Es konnten keine Tabellenlisten von der >> Datenquelle bezogen werden"). >> >> using driver .152 >> >> thanks for any hint. >> >> >> mit freundlichen Grüßen, André Knappstein EDV und Controlling ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ beta Eigenheim- und Grundstücksverwertungsgesellschaft mbH Hafenweg 4 59192 Bergkamen-Rünthe Telefon: +49 2389 9240 140 Telefax: +49 2389 9240 150 e-mail: kna...@be... Amtsgericht Hamm Nr. B 420 Geschäftsführer: Achim Krähling, Dirk Salewski und Matthias Steinhaus USt-IDNr.: DE 125215402 |
|
From: André K. <Kna...@be...> - 2013-03-22 12:19:42
|
Alexander, I am probably not too good in providing what you need to help me, so if the following is not sufficient, please ask for more. I will describe the steps leading to the error. I suppose that the database itself and the ODBC DSN are fine because they work well in other applications. 1.) Open MSWord (2007) (SP3) 2.) Select tab "Mailings" 3.) Select "Select recipients" (or similar label...) 3.) Select "use an existing list" 4.) Select "New Datasource" 5.) Select "ODBC/DSN" from the list 6.) Select any valid ODBC-DSN pointing to any Firebird database german error message: Es konnten keine Tabellenlisten von der Datenquelle bezogen werden (Unable to retrieve table metadata from data source) > Hi, > Tell in-depth information how to reproduce your problem please. > On 20.03.2013 17:28, André Knappstein wrote: >> Hi Gang! >> >> Is there a known technical reason why I can open literally any ODBC >> driven data source in MS Word (2007 and higher), but *not* Firebird? >> >> Do I have to make any settings which escaped me so far, or will it >> just not work or is the problem widely unknown so far? I'd like to >> prepare some views in Firebird and make them available for some >> assistants (creating mail merges). >> >> There is no problem in MS Excel (via MSQuery), but using the same >> *.dqy throws "unable to connect to datasource: library 'C:\program >> files\Firebi' failed to load", with an additional information >> "SQL-Status 08004, return code: SQL_ERROR". >> >> Creating a new connection throws "Unable to retrieve table metadata" >> (original in German: "Es konnten keine Tabellenlisten von der >> Datenquelle bezogen werden"). >> >> using driver .152 >> >> thanks for any hint. >> >> >> mit freundlichen Grüßen, André Knappstein EDV und Controlling ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ beta Eigenheim- und Grundstücksverwertungsgesellschaft mbH Hafenweg 4 59192 Bergkamen-Rünthe Telefon: +49 2389 9240 140 Telefax: +49 2389 9240 150 e-mail: kna...@be... Amtsgericht Hamm Nr. B 420 Geschäftsführer: Achim Krähling, Dirk Salewski und Matthias Steinhaus USt-IDNr.: DE 125215402 |
|
From: Alexander P. <ale...@gm...> - 2013-03-21 20:23:10
|
Hi, Tell in-depth information how to reproduce your problem please. On 20.03.2013 17:28, André Knappstein wrote: > Hi Gang! > > Is there a known technical reason why I can open literally any ODBC > driven data source in MS Word (2007 and higher), but *not* Firebird? > > Do I have to make any settings which escaped me so far, or will it > just not work or is the problem widely unknown so far? I'd like to > prepare some views in Firebird and make them available for some > assistants (creating mail merges). > > There is no problem in MS Excel (via MSQuery), but using the same > *.dqy throws "unable to connect to datasource: library 'C:\program > files\Firebi' failed to load", with an additional information > "SQL-Status 08004, return code: SQL_ERROR". > > Creating a new connection throws "Unable to retrieve table metadata" > (original in German: "Es konnten keine Tabellenlisten von der > Datenquelle bezogen werden"). > > using driver .152 > > thanks for any hint. > > > -- Alexander Potapchenko Team leader LASP Technologies, http://www.lasptech.ru |
|
From: André K. <Kna...@be...> - 2013-03-21 11:57:54
|
>> Is there a known technical reason why I can open literally any ODBC >> driven data source in MS Word (2007 and higher), but *not* Firebird? >> >> Do I have to make any settings which escaped me so far, or will it >> just not work or is the problem widely unknown so far? I'd like to >> prepare some views in Firebird and make them available for some >> assistants (creating mail merges). >> >> There is no problem in MS Excel (via MSQuery), but using the same >> *.dqy throws "unable to connect to datasource: library 'C:\program >> files\Firebi' failed to load", with an additional information >> "SQL-Status 08004, return code: SQL_ERROR". >> >> Creating a new connection throws "Unable to retrieve table metadata" >> (original in German: "Es konnten keine Tabellenlisten von der >> Datenquelle bezogen werden"). > What Firebird user are you using for connecting? Is it SYSDBA or the > database owner? SYSDBA for the first test. |
|
From: Thomas S. <ts...@ib...> - 2013-03-20 19:32:30
|
> Is there a known technical reason why I can open literally any ODBC > driven data source in MS Word (2007 and higher), but *not* Firebird? > > Do I have to make any settings which escaped me so far, or will it > just not work or is the problem widely unknown so far? I'd like to > prepare some views in Firebird and make them available for some > assistants (creating mail merges). > > There is no problem in MS Excel (via MSQuery), but using the same > *.dqy throws "unable to connect to datasource: library 'C:\program > files\Firebi' failed to load", with an additional information > "SQL-Status 08004, return code: SQL_ERROR". > > Creating a new connection throws "Unable to retrieve table metadata" > (original in German: "Es konnten keine Tabellenlisten von der > Datenquelle bezogen werden"). What Firebird user are you using for connecting? Is it SYSDBA or the database owner? -- With regards, Thomas Steinmaurer http://www.upscene.com/ |
|
From: André K. <Kna...@be...> - 2013-03-20 14:35:33
|
Thanks for the reply, Maury. Sorry for not specifying this from the beginning. Problem is in 32-Bit-only OS, Win7. Did not even try on 64-Bit Did try with a locally installed 32-Bit 2.5 Superserver and a remote 1.5.6 Classic Server. >> Hi Gang! >> >> Is there a known technical reason why I can open literally any ODBC >> driven data source in MS Word (2007 and higher), but *not* Firebird? > This may be a problem with 32-bit vs. 64-bit versions of the connector. > A number of components of the MS stack are still 32-bit only. This > includes MS Query, and I believe may be true for VBA in general, or at least it's ADO resources. > You may wish to try installing both the 32-bit and 64-bit versions, > making separate DSN's for them, and seeing if that helps. > On 2013-03-20, at 9:28 AM, André Knappstein wrote: > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Maury M. <mau...@gm...> - 2013-03-20 13:32:14
|
> Hi Gang! > > Is there a known technical reason why I can open literally any ODBC > driven data source in MS Word (2007 and higher), but *not* Firebird? This may be a problem with 32-bit vs. 64-bit versions of the connector. A number of components of the MS stack are still 32-bit only. This includes MS Query, and I believe may be true for VBA in general, or at least it's ADO resources. You may wish to try installing both the 32-bit and 64-bit versions, making separate DSN's for them, and seeing if that helps. On 2013-03-20, at 9:28 AM, André Knappstein wrote: |
|
From: André K. <Kna...@be...> - 2013-03-20 13:26:50
|
Hi Gang! Is there a known technical reason why I can open literally any ODBC driven data source in MS Word (2007 and higher), but *not* Firebird? Do I have to make any settings which escaped me so far, or will it just not work or is the problem widely unknown so far? I'd like to prepare some views in Firebird and make them available for some assistants (creating mail merges). There is no problem in MS Excel (via MSQuery), but using the same *.dqy throws "unable to connect to datasource: library 'C:\program files\Firebi' failed to load", with an additional information "SQL-Status 08004, return code: SQL_ERROR". Creating a new connection throws "Unable to retrieve table metadata" (original in German: "Es konnten keine Tabellenlisten von der Datenquelle bezogen werden"). using driver .152 thanks for any hint. |
|
From: Bob T. <web...@rw...> - 2013-03-13 20:27:47
|
Here is my setup: WI-V6.3.2.26539 Firebird 2.5 Firebird_ODBC_2.0.1.152_Win32 Alpha Five version 11 build 3353 FB Column Definition = BLOB SUB_TYPE 0 I can successfully see blob (JPG images) values that have been inserted into the database. However, if I attempt to insert a new image I get this Alpha Five error: Server side error inserting row. Internal Error - Invalid data index while putting long data. Here are some of the details from the ODBC trace: alpha5 201c-1f40 ENTER SQLPrepare HSTMT 0x027738B8 UCHAR * 0x1E74B7C0 [ 81] "INSERT INTO EMPLOYEE_PICTURES (EMP_PIC_ID, EMP_ID, EMP_PICTURE) VALUES (?, ?, ?)" SDWORD 81 alpha5 201c-1f40 EXIT SQLPrepare with return code 0 (SQL_SUCCESS) HSTMT 0x027738B8 UCHAR * 0x1E74B7C0 [ 81] "INSERT INTO EMPLOYEE_PICTURES (EMP_PIC_ID, EMP_ID, EMP_PICTURE) VALUES (?, ?, ?)" SDWORD 81 alpha5 201c-1f40 ENTER SQLBindParameter HSTMT 0x027738B8 UWORD 1 SWORD 1 <SQL_PARAM_INPUT> SWORD 8 <SQL_C_DOUBLE> SWORD 8 <SQL_DOUBLE> SQLULEN 8 SWORD 0 PTR 0x1E753A20 SQLLEN 8 SQLLEN * 0x1E753A28 alpha5 201c-1f40 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS) HSTMT 0x027738B8 UWORD 1 SWORD 1 <SQL_PARAM_INPUT> SWORD 8 <SQL_C_DOUBLE> SWORD 8 <SQL_DOUBLE> SQLULEN 8 SWORD 0 PTR 0x1E753A20 SQLLEN 8 SQLLEN * 0x1E753A28 (8) alpha5 201c-1f40 ENTER SQLBindParameter HSTMT 0x027738B8 UWORD 2 SWORD 1 <SQL_PARAM_INPUT> SWORD 8 <SQL_C_DOUBLE> SWORD 8 <SQL_DOUBLE> SQLULEN 8 SWORD 0 PTR 0x1E753A2C SQLLEN 8 SQLLEN * 0x1E753A34 alpha5 201c-1f40 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS) HSTMT 0x027738B8 UWORD 2 SWORD 1 <SQL_PARAM_INPUT> SWORD 8 <SQL_C_DOUBLE> SWORD 8 <SQL_DOUBLE> SQLULEN 8 SWORD 0 PTR 0x1E753A2C SQLLEN 8 SQLLEN * 0x1E753A34 (8) alpha5 201c-1f40 ENTER SQLBindParameter HSTMT 0x027738B8 UWORD 3 SWORD 1 <SQL_PARAM_INPUT> SWORD -2 <SQL_C_BINARY> SWORD -4 <SQL_LONGVARBINARY> SQLULEN 23588 SWORD 0 PTR 0x1E753A38 SQLLEN 47178 SQLLEN * 0x1E753A40 alpha5 201c-1f40 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS) HSTMT 0x027738B8 UWORD 3 SWORD 1 <SQL_PARAM_INPUT> SWORD -2 <SQL_C_BINARY> SWORD -4 <SQL_LONGVARBINARY> SQLULEN 23588 SWORD 0 PTR 0x1E753A38 SQLLEN 47178 SQLLEN * 0x1E753A40 (-100) alpha5 201c-1f40 ENTER SQLExecute HSTMT 0x027738B8 alpha5 201c-1f40 EXIT SQLExecute with return code 99 (SQL_NEED_DATA) HSTMT 0x027738B8 alpha5 201c-1f40 ENTER SQLParamData HSTMT 0x027738B8 PTR * 0x00CD62DC alpha5 201c-1f40 EXIT SQLParamData with return code 99 (SQL_NEED_DATA) HSTMT 0x027738B8 PTR * 0x00CD62DC alpha5 201c-1f40 ENTER SQLPutData HSTMT 0x027738B8 PTR 0x1E7D52D0 SQLLEN 23587 Is this a problem with the ODBC driver? Thanks, Bob |
|
From: André K. <Kna...@be...> - 2013-03-07 11:56:12
|
I know that this is problem caused by very bad design by MS. But maybe someone already found a workaround and would share it here. I need to call the same DSN sometimes from a 32-Bit application, and sometimes from a 64-Bit application. So I need a DSN with the same name once created with the 32-Bit ODBCAD32.exe and once with the 64-Bit ODBCAD32.exe. One therefore has to reference the 32-Bit version of FBClient.dll and the other references the 64-Bit version. No problem for System DSNs. The different settings do not mess with each other. For User-DSNs though, you must decide whether a DSN is either 32- or 64-Bit because no matter which version of ODBCAD32.exe you are using to create/manage the DSNs, they will both be stored in the very same registry key, which basically means that any setting in either ODBCAD32.exe will overwrite the other, and therefore the last selected version of FBClient.dll will win. Sounds like there is no solution for this, and I can't even start to imagine which idiot in Redmond let that pass. But, anyway, did anybody of you stumble across some workaround, maybe involving some system hacks? I frankly do not even know where all the places are where some 3rd party tool is making a call to a User-DSN. Users even can create their own Excel/LibreOffice/CrystalReport connections based on an existing User-DSN. thanks, André |
|
From: Werner F. B. <wer...@fr...> - 2013-03-05 12:34:52
|
Hi, Got a solution on the InnoSetup list. I had a quote to many. But I also learned about the "regserver" flag which is a much better way of handling the registration in an InnoSetup installer. Werner On 05/03/2013 13:19, Werner F. Bruhin wrote: > Hi, > > I have an InnoSetup installer which installs besides by application also > the FB ODBC driver, in case users want to access the db from e.g. > LibreOffice. > > On some machines I get the following error when the installer runs: > > LoadLibrary(c:\windows\system32\odbcfb.dll -s) failed to load > > On MS site a possible reason could be that a dependency is not present. > > But I doubt that is the reason as when I run the following manually, it > works. > > regsvr32 c:\windows\system32\odbcfb.dll > > Any pointers what might be wrong? > > Werner > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > > |
|
From: Werner F. B. <wer...@fr...> - 2013-03-05 12:18:04
|
Hi, I have an InnoSetup installer which installs besides by application also the FB ODBC driver, in case users want to access the db from e.g. LibreOffice. On some machines I get the following error when the installer runs: LoadLibrary(c:\windows\system32\odbcfb.dll -s) failed to load On MS site a possible reason could be that a dependency is not present. But I doubt that is the reason as when I run the following manually, it works. regsvr32 c:\windows\system32\odbcfb.dll Any pointers what might be wrong? Werner |
|
From: W O <sis...@gm...> - 2013-03-01 03:57:11
|
A similar problem happens with Visual FoxPro, the bigints fields of Firebird are translated as character(19) Why? No idea, but so it is. The solution is easy, the VAL() function solves the problem by casting the character(19) field to a numeric field, but at first it is annoying. I have to live with that. Greetings. Walter. On Thu, Feb 28, 2013 at 4:41 AM, <bjo...@fa...> wrote: > Hello, > > we stepped over a small problem with current odbc driver and MS > Access: > > BIGINT (in our Db primary keys) fields are presented as text 255 > fields in access. > > Trying another client via odbc they are presented as flaot fields > wich seems to be a littel bit better than text 255 but not what I'd > expect. > > Can anybody give me the info where there could be a problem and how > to get bigint as a number to access via odbc? > > There must be a problem in Access as I found people mentioning > similar problems with MS SQL Server and Access. > > > > > > Björn > > -- > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > |
|
From: <bjo...@fa...> - 2013-03-01 02:22:19
|
Hello,
we stepped over a small problem with current odbc driver and MS
Access:
BIGINT (in our Db primary keys) fields are presented as text 255
fields in access.
Trying another client via odbc they are presented as flaot fields
wich seems to be a littel bit better than text 255 but not what I'd
expect.
Can anybody give me the info where there could be a problem and how
to get bigint as a number to access via odbc?
There must be a problem in Access as I found people mentioning
similar problems with MS SQL Server and Access.
Björn
--
|
|
From: Jojakim <joj...@jo...> - 2013-02-27 14:10:47
|
Hello, In the past, I could login and use the firebird tracker w/o problem. Today I wanted to login again, and the system told me, that I may not login (no permission). Thought I used the wrong pwd, tried others, w/o success. Clicked on "forgot pwd", entered email, and then the system showed an exception message. Did not receive any email, tried again, now the system tells me, user does not exist. Checked the buglist of the ODBC project where I reported bugs recently: my clear name isn't shown any more, instead just my login name. Is there someone who can have a look on this please? Thanks. -- Joja |
|
From: Olaf K. <ola...@sa...> - 2013-02-27 09:16:14
|
Hello, I use firebird 2.1 cs and the 32 Bit newest ODBC Driver on Windows 7 x64. If I link my tables in ms access to my local database, it takes 4 seconds to open a query. Now If I link the tables to our Server (same fb version running), it takes one minute to open the same query. On Windows XP with the same configuration It takes only 5 seconds. What can I do? Perhaps it is possible to change some options on my odbc driver? What is safe thread? Some identifiers options? Thank you very much for hints and tips. Best regards. Olaf |
71 messages has been excluded from this view by a project administrator.
