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: Angel T. <ang...@gm...> - 2018-01-17 10:12:13
|
Hello, My name is Angel Tomov and I am a BI developer. My latest client is using Firebird 2.5 database. I have downloaded firebird ODBC drivers and Firebird .dll’s from https://firebirdsql.org/en/odbc-driver/ My machine is x64, so I downloaded odbc x64. After I have installed the driver and copy/paste the .dll’s from OdbcFb_DLL_2.0.5.156_x64.zip into Windows/System32 Whenever I try to test the connection, ODBC administrator crashes. I have Administrator Rights, and I am using Windows Server 2016. I have tried with both, x32 and x64. Any help will be highly appreciated, Sincerely Yours, Angel Tomov Sent from Mail for Windows 10 |
|
From: Alexander P. <ale...@gm...> - 2017-10-16 17:21:01
|
If gds32.dll is not found then fbclient.dll is loaded by default too. On 16.10.2017 18:06, Jorge Andres Brugger wrote: > Thanks Alexander! > The use of gds32 is related to keeping support to interbase? (I would > prefer fbclient.dll to be the default library, as I usually dont > intall gds32 with my programs). > I would also happy if the default value for quoted identifiers is "NO" > (I.m not sure why someone will prefer quoted identififiers over > non-quoted ones) > Regards! > > 2017-10-14 9:18 GMT-03:00 Alexander Potapchenko > <ale...@gm... > <mailto:ale...@gm...>>: > > Jorge, > > You can see all default values in new DSN Windows dialog > Client will be gds32.dll, Driver is not used now. > > > On 13.10.2017 20:34, Jorge Andres Brugger wrote: >> I can write a connectoin string like >> "DRIVER=Firebird/InterBase(r) >> driver;UID=SYSDBA;PWD=masterkey;DBNAME=server:database" and works. >> But there are several configurable parameters, acording to odbc >> driver docs: >> >> *Verbose keyword* *Short form* >> Database Account *UID* or *USER* >> Password *PWD* or *PASSWORD* >> Role *ROLE* >> Data Source Name *DSN* >> Driver *DRIVER* >> Database *DBNAME* or *DATABASE* >> Client *CLIENT* >> Character Set *CHARSET* or *CHARACTERSET* >> Set read only *READONLY* >> Set nowait *NOWAIT* >> Dialect *DIALECT* >> Set quoted identifier *QUOTED* >> Set sensitive identifier *SENSITIVE* >> Set auto quoted identifier *AUTOQUOTED* >> File DSN *FILEDSN* >> Save DSN *SAVEDSN* >> >> >> It not defined explicitly, what are the default values for each >> attribute? (I´m interested particularly in those which admit >> "Y/N" values. >> Thanks! >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org!http://sdm.link/slashdot >> >> >> _______________________________________________ >> Firebird-odbc-devel mailing list >> Fir...@li... <mailto:Fir...@li...> >> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel <https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel> > > > -- > Alexander Potapchenko > Team leader > LASP Technologies, http://www.lasptech.ru > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > <mailto:Fir...@li...> > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > <https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel> > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel -- Alexander Potapchenko |
|
From: Jorge A. B. <jor...@gm...> - 2017-10-16 15:06:11
|
Thanks Alexander! The use of gds32 is related to keeping support to interbase? (I would prefer fbclient.dll to be the default library, as I usually dont intall gds32 with my programs). I would also happy if the default value for quoted identifiers is "NO" (I.m not sure why someone will prefer quoted identififiers over non-quoted ones) Regards! 2017-10-14 9:18 GMT-03:00 Alexander Potapchenko < ale...@gm...>: > Jorge, > > You can see all default values in new DSN Windows dialog > Client will be gds32.dll, Driver is not used now. > > > On 13.10.2017 20:34, Jorge Andres Brugger wrote: > > I can write a connectoin string like "DRIVER=Firebird/InterBase(r) > driver;UID=SYSDBA;PWD=masterkey;DBNAME=server:database" and works. > But there are several configurable parameters, acording to odbc driver > docs: > > *Verbose keyword* *Short form* > Database Account *UID* or *USER* > Password *PWD* or *PASSWORD* > Role *ROLE* > Data Source Name *DSN* > Driver *DRIVER* > Database *DBNAME* or *DATABASE* > Client *CLIENT* > Character Set *CHARSET* or *CHARACTERSET* > Set read only *READONLY* > Set nowait *NOWAIT* > Dialect *DIALECT* > Set quoted identifier *QUOTED* > Set sensitive identifier *SENSITIVE* > Set auto quoted identifier *AUTOQUOTED* > File DSN *FILEDSN* > Save DSN *SAVEDSN* > It not defined explicitly, what are the default values for each attribute? > (I´m interested particularly in those which admit "Y/N" values. > Thanks! > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Firebird-odbc-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > > > > -- > Alexander Potapchenko > Team leader > LASP Technologies, http://www.lasptech.ru > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > > |
|
From: Alexander P. <ale...@gm...> - 2017-10-14 12:18:14
|
Jorge, You can see all default values in new DSN Windows dialog Client will be gds32.dll, Driver is not used now. On 13.10.2017 20:34, Jorge Andres Brugger wrote: > I can write a connectoin string like "DRIVER=Firebird/InterBase(r) > driver;UID=SYSDBA;PWD=masterkey;DBNAME=server:database" and works. > But there are several configurable parameters, acording to odbc driver > docs: > > *Verbose keyword* *Short form* > Database Account *UID* or *USER* > Password *PWD* or *PASSWORD* > Role *ROLE* > Data Source Name *DSN* > Driver *DRIVER* > Database *DBNAME* or *DATABASE* > Client *CLIENT* > Character Set *CHARSET* or *CHARACTERSET* > Set read only *READONLY* > Set nowait *NOWAIT* > Dialect *DIALECT* > Set quoted identifier *QUOTED* > Set sensitive identifier *SENSITIVE* > Set auto quoted identifier *AUTOQUOTED* > File DSN *FILEDSN* > Save DSN *SAVEDSN* > > > It not defined explicitly, what are the default values for each > attribute? (I´m interested particularly in those which admit "Y/N" values. > Thanks! > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel -- Alexander Potapchenko Team leader LASP Technologies, http://www.lasptech.ru |
|
From: Jorge A. B. <jor...@gm...> - 2017-10-13 17:34:36
|
I can write a connectoin string like "DRIVER=Firebird/InterBase(r) driver;UID=SYSDBA;PWD=masterkey;DBNAME=server:database" and works. But there are several configurable parameters, acording to odbc driver docs: *Verbose keyword* *Short form* Database Account *UID* or *USER* Password *PWD* or *PASSWORD* Role *ROLE* Data Source Name *DSN* Driver *DRIVER* Database *DBNAME* or *DATABASE* Client *CLIENT* Character Set *CHARSET* or *CHARACTERSET* Set read only *READONLY* Set nowait *NOWAIT* Dialect *DIALECT* Set quoted identifier *QUOTED* Set sensitive identifier *SENSITIVE* Set auto quoted identifier *AUTOQUOTED* File DSN *FILEDSN* Save DSN *SAVEDSN* It not defined explicitly, what are the default values for each attribute? (I´m interested particularly in those which admit "Y/N" values. Thanks! |
|
From: Nick C. <ni...@yo...> - 2017-09-25 08:30:28
|
Mine is slightly older, Office Pro Plus 2016 Version 1707 8326.2107. Pretty frustrating really, I think that it has been about 6 months since I started having the problem with no idea of what caused it or how to fix it. At least it is all running now and fortunately I would work around the need to link to two database over this time. Cheerio Nick m. 0274 433 732 w. www.yourqs.co.nz -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Monday, 25 September 2017 7:44 PM To: ni...@yo...; fir...@li... Subject: RE: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Hi, Just tried out my "crash test" files, and they all pass now too! Nice, but also a bit scary, if solutions can break like that with no info available anywhere and not knowing if the issue will be solved or when it is solved. Thanks for the heads up - let's see how long it lasts. Here is the version I use that seems to work now: Office 365 Pro Plus Version 1708 (build: 8431.2079 Click-to-Run) Monthly Channel kr Morten -----Original Message----- From: Nick Clements [mailto:ni...@yo...] Sent: 2017-09-25 06:23 To: 'Morten H Pedersen' <ho...@gm...>; fir...@li... Subject: RE: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Hi Morten, My Office suite just updated today and they problem seems to have gone. I went into the database that I have had problems with and could open tables from two ODBC sources and it didn't crash. So it must have been a Microsoft problem that they have resolved. Fingers crossed anyway. Cheerio Nick m. 0274 433 732 w. www.yourqs.co.nz -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Wednesday, 13 September 2017 11:08 PM To: ni...@yo...; fir...@li... Subject: RE: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Hi Nick, Did you get any further with this? I have tried Microsoft, but no luck yet. /Morten -----Original Message----- From: Nick Clements [mailto:ni...@yo...] Sent: 2017-09-06 23:32 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Thanks for the help (attempts anyway). My Access version is 2016 and is 32bit. I can't comment on MySQL as I'm only using MS Access with FB. I accept it is possibly a Microsoft issue but I'm guessing that it was an MS Access upgrade that has caused the change (I subsequently updated the ODBC drivers to see if it would help). However, I'm not very confident that Microsoft will care in the least hence pursing the FB route for a solution. I'm not sure how the drivers determine whether to use 32bit or 64bit as there is no option to choose 32 or 64 when creating a new source. When I open the option with MS Access to select a linked table, you just get presented with a list of databases to choose from. I can open both the 32 and 64bit ODBC Data Source Administrators from Windows and they both show the same content so I'm guessing that Windows must either create both, or they can work with both simultaneously. I'd assume that as Access is 32bit it is selecting the 32 bit ones. I have being doing exactly the same thing with MS Access and multiple FB databases for about 15 years without an issue. Now if I have two tables linked from two identical FB databases I can open tables in from either in separate sessions, (I.e. Open one table from the first source, close Access, then open a table from the second source) but if I try to open a table from a second source in the same session it always crashes. I'm not sure what is changed but a memory clash would seem like a potential cause for this. I'm happy to provide sample databases (2 x FB and 1x MS Access) if anyone wants to dig further into this. I might try seeing if I can install Access 2013 somewhere and try it in that. Might help isolate the problem. Cheerio Nick -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Thursday, 7 September 2017 1:24 AM To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs I have now tried the same with MySQL ODBC driver, connecting to two different tables in each of the three different databases (i.e. 6 tables) on same server using 3 different / unique ODBC data sources. This works without any issues. When you get to the third ODBC source with the FB connector, it crashes when looking at the data or when starting the load. Could there be any memory clash (a shared static variable or something in the FB connector code?) I have three active ODBC sources using the FB ODBC connector. I can load data from any combination of two sources without any issues. As soon as I touch a third, Access crashes. That is not an issue with the MySQL connector. I tried to toggle between fbclient.dll and gds32.dll - no apparent difference. I tried with the "read" checkmark on and off - no difference. Access crashes when you add the third ODBC connection. Only differences I can see are : FB ODBC connecter is both 32 and 64 bit. Is it in the same dll or are there two and how do you choose between the two (my Access and Excel are both 32 bit on Windows 10 64-bit)? kind regards, Morten Høgholm Pedersen -----Original Message----- From: Dimitry Sibiryakov [mailto:sd...@ib...] Sent: 2017-09-06 13:27 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs 06.09.2017 13:23, Morten H Pedersen wrote: > here is what I got debugging from Visual > Studio: I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. -- WBR, SD. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel --- This email has been checked for viruses by AVG. http://www.avg.com ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Morten H P. <ho...@gm...> - 2017-09-25 06:44:03
|
Hi, Just tried out my "crash test" files, and they all pass now too! Nice, but also a bit scary, if solutions can break like that with no info available anywhere and not knowing if the issue will be solved or when it is solved. Thanks for the heads up - let's see how long it lasts. Here is the version I use that seems to work now: Office 365 Pro Plus Version 1708 (build: 8431.2079 Click-to-Run) Monthly Channel kr Morten -----Original Message----- From: Nick Clements [mailto:ni...@yo...] Sent: 2017-09-25 06:23 To: 'Morten H Pedersen' <ho...@gm...>; fir...@li... Subject: RE: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Hi Morten, My Office suite just updated today and they problem seems to have gone. I went into the database that I have had problems with and could open tables from two ODBC sources and it didn't crash. So it must have been a Microsoft problem that they have resolved. Fingers crossed anyway. Cheerio Nick m. 0274 433 732 w. www.yourqs.co.nz -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Wednesday, 13 September 2017 11:08 PM To: ni...@yo...; fir...@li... Subject: RE: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Hi Nick, Did you get any further with this? I have tried Microsoft, but no luck yet. /Morten -----Original Message----- From: Nick Clements [mailto:ni...@yo...] Sent: 2017-09-06 23:32 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Thanks for the help (attempts anyway). My Access version is 2016 and is 32bit. I can't comment on MySQL as I'm only using MS Access with FB. I accept it is possibly a Microsoft issue but I'm guessing that it was an MS Access upgrade that has caused the change (I subsequently updated the ODBC drivers to see if it would help). However, I'm not very confident that Microsoft will care in the least hence pursing the FB route for a solution. I'm not sure how the drivers determine whether to use 32bit or 64bit as there is no option to choose 32 or 64 when creating a new source. When I open the option with MS Access to select a linked table, you just get presented with a list of databases to choose from. I can open both the 32 and 64bit ODBC Data Source Administrators from Windows and they both show the same content so I'm guessing that Windows must either create both, or they can work with both simultaneously. I'd assume that as Access is 32bit it is selecting the 32 bit ones. I have being doing exactly the same thing with MS Access and multiple FB databases for about 15 years without an issue. Now if I have two tables linked from two identical FB databases I can open tables in from either in separate sessions, (I.e. Open one table from the first source, close Access, then open a table from the second source) but if I try to open a table from a second source in the same session it always crashes. I'm not sure what is changed but a memory clash would seem like a potential cause for this. I'm happy to provide sample databases (2 x FB and 1x MS Access) if anyone wants to dig further into this. I might try seeing if I can install Access 2013 somewhere and try it in that. Might help isolate the problem. Cheerio Nick -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Thursday, 7 September 2017 1:24 AM To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs I have now tried the same with MySQL ODBC driver, connecting to two different tables in each of the three different databases (i.e. 6 tables) on same server using 3 different / unique ODBC data sources. This works without any issues. When you get to the third ODBC source with the FB connector, it crashes when looking at the data or when starting the load. Could there be any memory clash (a shared static variable or something in the FB connector code?) I have three active ODBC sources using the FB ODBC connector. I can load data from any combination of two sources without any issues. As soon as I touch a third, Access crashes. That is not an issue with the MySQL connector. I tried to toggle between fbclient.dll and gds32.dll - no apparent difference. I tried with the "read" checkmark on and off - no difference. Access crashes when you add the third ODBC connection. Only differences I can see are : FB ODBC connecter is both 32 and 64 bit. Is it in the same dll or are there two and how do you choose between the two (my Access and Excel are both 32 bit on Windows 10 64-bit)? kind regards, Morten Høgholm Pedersen -----Original Message----- From: Dimitry Sibiryakov [mailto:sd...@ib...] Sent: 2017-09-06 13:27 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs 06.09.2017 13:23, Morten H Pedersen wrote: > here is what I got debugging from Visual > Studio: I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. -- WBR, SD. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel --- This email has been checked for viruses by AVG. http://www.avg.com ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Nick C. <ni...@yo...> - 2017-09-25 04:22:48
|
Hi Morten, My Office suite just updated today and they problem seems to have gone. I went into the database that I have had problems with and could open tables from two ODBC sources and it didn't crash. So it must have been a Microsoft problem that they have resolved. Fingers crossed anyway. Cheerio Nick m. 0274 433 732 w. www.yourqs.co.nz -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Wednesday, 13 September 2017 11:08 PM To: ni...@yo...; fir...@li... Subject: RE: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Hi Nick, Did you get any further with this? I have tried Microsoft, but no luck yet. /Morten -----Original Message----- From: Nick Clements [mailto:ni...@yo...] Sent: 2017-09-06 23:32 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Thanks for the help (attempts anyway). My Access version is 2016 and is 32bit. I can't comment on MySQL as I'm only using MS Access with FB. I accept it is possibly a Microsoft issue but I'm guessing that it was an MS Access upgrade that has caused the change (I subsequently updated the ODBC drivers to see if it would help). However, I'm not very confident that Microsoft will care in the least hence pursing the FB route for a solution. I'm not sure how the drivers determine whether to use 32bit or 64bit as there is no option to choose 32 or 64 when creating a new source. When I open the option with MS Access to select a linked table, you just get presented with a list of databases to choose from. I can open both the 32 and 64bit ODBC Data Source Administrators from Windows and they both show the same content so I'm guessing that Windows must either create both, or they can work with both simultaneously. I'd assume that as Access is 32bit it is selecting the 32 bit ones. I have being doing exactly the same thing with MS Access and multiple FB databases for about 15 years without an issue. Now if I have two tables linked from two identical FB databases I can open tables in from either in separate sessions, (I.e. Open one table from the first source, close Access, then open a table from the second source) but if I try to open a table from a second source in the same session it always crashes. I'm not sure what is changed but a memory clash would seem like a potential cause for this. I'm happy to provide sample databases (2 x FB and 1x MS Access) if anyone wants to dig further into this. I might try seeing if I can install Access 2013 somewhere and try it in that. Might help isolate the problem. Cheerio Nick -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Thursday, 7 September 2017 1:24 AM To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs I have now tried the same with MySQL ODBC driver, connecting to two different tables in each of the three different databases (i.e. 6 tables) on same server using 3 different / unique ODBC data sources. This works without any issues. When you get to the third ODBC source with the FB connector, it crashes when looking at the data or when starting the load. Could there be any memory clash (a shared static variable or something in the FB connector code?) I have three active ODBC sources using the FB ODBC connector. I can load data from any combination of two sources without any issues. As soon as I touch a third, Access crashes. That is not an issue with the MySQL connector. I tried to toggle between fbclient.dll and gds32.dll - no apparent difference. I tried with the "read" checkmark on and off - no difference. Access crashes when you add the third ODBC connection. Only differences I can see are : FB ODBC connecter is both 32 and 64 bit. Is it in the same dll or are there two and how do you choose between the two (my Access and Excel are both 32 bit on Windows 10 64-bit)? kind regards, Morten Høgholm Pedersen -----Original Message----- From: Dimitry Sibiryakov [mailto:sd...@ib...] Sent: 2017-09-06 13:27 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs 06.09.2017 13:23, Morten H Pedersen wrote: > here is what I got debugging from Visual > Studio: I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. -- WBR, SD. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel --- This email has been checked for viruses by AVG. http://www.avg.com ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Morten H P. <ho...@gm...> - 2017-09-13 11:08:41
|
Hi Nick, Did you get any further with this? I have tried Microsoft, but no luck yet. /Morten -----Original Message----- From: Nick Clements [mailto:ni...@yo...] Sent: 2017-09-06 23:32 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs Thanks for the help (attempts anyway). My Access version is 2016 and is 32bit. I can't comment on MySQL as I'm only using MS Access with FB. I accept it is possibly a Microsoft issue but I'm guessing that it was an MS Access upgrade that has caused the change (I subsequently updated the ODBC drivers to see if it would help). However, I'm not very confident that Microsoft will care in the least hence pursing the FB route for a solution. I'm not sure how the drivers determine whether to use 32bit or 64bit as there is no option to choose 32 or 64 when creating a new source. When I open the option with MS Access to select a linked table, you just get presented with a list of databases to choose from. I can open both the 32 and 64bit ODBC Data Source Administrators from Windows and they both show the same content so I'm guessing that Windows must either create both, or they can work with both simultaneously. I'd assume that as Access is 32bit it is selecting the 32 bit ones. I have being doing exactly the same thing with MS Access and multiple FB databases for about 15 years without an issue. Now if I have two tables linked from two identical FB databases I can open tables in from either in separate sessions, (I.e. Open one table from the first source, close Access, then open a table from the second source) but if I try to open a table from a second source in the same session it always crashes. I'm not sure what is changed but a memory clash would seem like a potential cause for this. I'm happy to provide sample databases (2 x FB and 1x MS Access) if anyone wants to dig further into this. I might try seeing if I can install Access 2013 somewhere and try it in that. Might help isolate the problem. Cheerio Nick -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Thursday, 7 September 2017 1:24 AM To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs I have now tried the same with MySQL ODBC driver, connecting to two different tables in each of the three different databases (i.e. 6 tables) on same server using 3 different / unique ODBC data sources. This works without any issues. When you get to the third ODBC source with the FB connector, it crashes when looking at the data or when starting the load. Could there be any memory clash (a shared static variable or something in the FB connector code?) I have three active ODBC sources using the FB ODBC connector. I can load data from any combination of two sources without any issues. As soon as I touch a third, Access crashes. That is not an issue with the MySQL connector. I tried to toggle between fbclient.dll and gds32.dll - no apparent difference. I tried with the "read" checkmark on and off - no difference. Access crashes when you add the third ODBC connection. Only differences I can see are : FB ODBC connecter is both 32 and 64 bit. Is it in the same dll or are there two and how do you choose between the two (my Access and Excel are both 32 bit on Windows 10 64-bit)? kind regards, Morten Høgholm Pedersen -----Original Message----- From: Dimitry Sibiryakov [mailto:sd...@ib...] Sent: 2017-09-06 13:27 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs 06.09.2017 13:23, Morten H Pedersen wrote: > here is what I got debugging from Visual > Studio: I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. -- WBR, SD. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel --- This email has been checked for viruses by AVG. http://www.avg.com ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Morten H. P. <ho...@gm...> - 2017-09-07 05:24:49
|
I don't know really how an ODBC driver is made and if it does not return any pointers, any data elements with associated lengths, or share any memory with msaccess then the ODBC driver might not be the reason but otherwise a faulty pointer, wrong array lenghts or shared objects could make msaccess crash even when not running any code in the Firebird ODBC driver, right? Kr Morten > On 6 Sep 2017, at 13.27, Dimitry Sibiryakov <sd...@ib...> wrote: > > 06.09.2017 13:23, Morten H Pedersen wrote: >> here is what I got debugging from Visual >> Studio: > > I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. > > > -- > WBR, SD. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Nick C. <ni...@yo...> - 2017-09-06 22:02:58
|
Thanks for the help (attempts anyway). My Access version is 2016 and is 32bit. I can't comment on MySQL as I'm only using MS Access with FB. I accept it is possibly a Microsoft issue but I'm guessing that it was an MS Access upgrade that has caused the change (I subsequently updated the ODBC drivers to see if it would help). However, I'm not very confident that Microsoft will care in the least hence pursing the FB route for a solution. I'm not sure how the drivers determine whether to use 32bit or 64bit as there is no option to choose 32 or 64 when creating a new source. When I open the option with MS Access to select a linked table, you just get presented with a list of databases to choose from. I can open both the 32 and 64bit ODBC Data Source Administrators from Windows and they both show the same content so I'm guessing that Windows must either create both, or they can work with both simultaneously. I'd assume that as Access is 32bit it is selecting the 32 bit ones. I have being doing exactly the same thing with MS Access and multiple FB databases for about 15 years without an issue. Now if I have two tables linked from two identical FB databases I can open tables in from either in separate sessions, (I.e. Open one table from the first source, close Access, then open a table from the second source) but if I try to open a table from a second source in the same session it always crashes. I'm not sure what is changed but a memory clash would seem like a potential cause for this. I'm happy to provide sample databases (2 x FB and 1x MS Access) if anyone wants to dig further into this. I might try seeing if I can install Access 2013 somewhere and try it in that. Might help isolate the problem. Cheerio Nick -----Original Message----- From: Morten H Pedersen [mailto:ho...@gm...] Sent: Thursday, 7 September 2017 1:24 AM To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs I have now tried the same with MySQL ODBC driver, connecting to two different tables in each of the three different databases (i.e. 6 tables) on same server using 3 different / unique ODBC data sources. This works without any issues. When you get to the third ODBC source with the FB connector, it crashes when looking at the data or when starting the load. Could there be any memory clash (a shared static variable or something in the FB connector code?) I have three active ODBC sources using the FB ODBC connector. I can load data from any combination of two sources without any issues. As soon as I touch a third, Access crashes. That is not an issue with the MySQL connector. I tried to toggle between fbclient.dll and gds32.dll - no apparent difference. I tried with the "read" checkmark on and off - no difference. Access crashes when you add the third ODBC connection. Only differences I can see are : FB ODBC connecter is both 32 and 64 bit. Is it in the same dll or are there two and how do you choose between the two (my Access and Excel are both 32 bit on Windows 10 64-bit)? kind regards, Morten Høgholm Pedersen -----Original Message----- From: Dimitry Sibiryakov [mailto:sd...@ib...] Sent: 2017-09-06 13:27 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs 06.09.2017 13:23, Morten H Pedersen wrote: > here is what I got debugging from Visual > Studio: I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. -- WBR, SD. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel --- This email has been checked for viruses by AVG. http://www.avg.com |
|
From: Morten H P. <ho...@gm...> - 2017-09-06 13:24:06
|
I have now tried the same with MySQL ODBC driver, connecting to two different tables in each of the three different databases (i.e. 6 tables) on same server using 3 different / unique ODBC data sources. This works without any issues. When you get to the third ODBC source with the FB connector, it crashes when looking at the data or when starting the load. Could there be any memory clash (a shared static variable or something in the FB connector code?) I have three active ODBC sources using the FB ODBC connector. I can load data from any combination of two sources without any issues. As soon as I touch a third, Access crashes. That is not an issue with the MySQL connector. I tried to toggle between fbclient.dll and gds32.dll - no apparent difference. I tried with the "read" checkmark on and off - no difference. Access crashes when you add the third ODBC connection. Only differences I can see are : FB ODBC connecter is both 32 and 64 bit. Is it in the same dll or are there two and how do you choose between the two (my Access and Excel are both 32 bit on Windows 10 64-bit)? kind regards, Morten Høgholm Pedersen -----Original Message----- From: Dimitry Sibiryakov [mailto:sd...@ib...] Sent: 2017-09-06 13:27 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs 06.09.2017 13:23, Morten H Pedersen wrote: > here is what I got debugging from Visual > Studio: I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. -- WBR, SD. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Paul R. <pr...@ib...> - 2017-09-06 11:55:54
|
On Wed, 6 Sep 2017 13:27:23 +0200 Dimitry Sibiryakov wrote > 06.09.2017 13:23, Morten H Pedersen wrote: > > here is what I got debugging from Visual > > Studio: > > I see no sign of Firebird ODBC here. I think this is a question > for MS support, not Firebird one. > > In my albeit limited experience, all the symbols need to be loaded otherwise the stack trace may be meaningless. Not always, but how can we know otherwise without all the symbols ? As the stack trace itself says... [Frames below may be incorrect and/or missing, no symbols loaded for ACECORE.DLL] Getting all the symbols loaded is another matter as all the symbols need to match up correctly to all the installed binaries. Especially as the released versions of the driver don't seem to include an option to download the pdb file. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird |
|
From: Dimitry S. <sd...@ib...> - 2017-09-06 11:27:29
|
06.09.2017 13:23, Morten H Pedersen wrote: > here is what I got debugging from Visual > Studio: I see no sign of Firebird ODBC here. I think this is a question for MS support, not Firebird one. -- WBR, SD. |
|
From: Morten H P. <ho...@gm...> - 2017-09-06 11:23:35
|
Hi Not a Windows debugging expert, here is what I got debugging from Visual Studio: Exception thrown at 0x19B26840 (ACECORE.DLL) in MSACCESS.EXE: 0xC0000005: Access violation reading location 0x00000018. occurred > ACECORE.DLL!19b26840() Unknown No symbols loaded. [Frames below may be incorrect and/or missing, no symbols loaded for ACECORE.DLL] Annotated Frame ACECORE.DLL!19b2695a() Unknown No symbols loaded. ACECORE.DLL!19a665fd() Unknown No symbols loaded. ACECORE.DLL!19a66a43() Unknown No symbols loaded. ACECORE.DLL!19a665fd() Unknown No symbols loaded. ACECORE.DLL!19a66795() Unknown No symbols loaded. ACECORE.DLL!19a65b7b() Unknown No symbols loaded. Mso20win32client.dll!5c79f51e() Unknown No symbols loaded. ACECORE.DLL!19a2d944() Unknown No symbols loaded. ACECORE.DLL!19a7cf31() Unknown No symbols loaded. ACECORE.DLL!19a47d58() Unknown No symbols loaded. ACECORE.DLL!19b6547d() Unknown No symbols loaded. ACECORE.DLL!19a289ab() Unknown No symbols loaded. ACECORE.DLL!19a28555() Unknown No symbols loaded. ACECORE.DLL!19b6417e() Unknown No symbols loaded. [External Code] Annotated Frame ACECORE.DLL!19a2c4bb() Unknown No symbols loaded. ACECORE.DLL!19a2bfbd() Unknown No symbols loaded. ACECORE.DLL!19a2c655() Unknown No symbols loaded. ACECORE.DLL!19a46c25() Unknown No symbols loaded. MSACCESS.EXE!00fba12e() Unknown No symbols loaded. MSACCESS.EXE!00a162c5() Unknown No symbols loaded. MSACCESS.EXE!009c2149() Unknown No symbols loaded. MSACCESS.EXE!00fbd8e9() Unknown No symbols loaded. MSACCESS.EXE!00f82891() Unknown No symbols loaded. MSACCESS.EXE!009c344f() Unknown No symbols loaded. Mso20win32client.dll!5c79f51e() Unknown No symbols loaded. [External Code] Annotated Frame tv_w32.dll!65f4bf7c() Unknown No symbols loaded. ACECORE.DLL!19a2dab4() Unknown No symbols loaded. MSACCESS.EXE!009c344f() Unknown No symbols loaded. MSACCESS.EXE!00a899d7() Unknown No symbols loaded. MSACCESS.EXE!009c3809() Unknown No symbols loaded. [External Code] Annotated Frame tv_w32.dll!65f4bf7c() Unknown No symbols loaded. Mso20win32client.dll!5c79f4a6() Unknown No symbols loaded. MSACCESS.EXE!009c344f() Unknown No symbols loaded. MSACCESS.EXE!00a899d7() Unknown No symbols loaded. Mso40UIwin32client.dll!5b3e50a2() Unknown No symbols loaded. MSACCESS.EXE!009c344f() Unknown No symbols loaded. Mso40UIwin32client.dll!5b3e50a2() Unknown No symbols loaded. Mso40UIwin32client.dll!5b3e50a2() Unknown No symbols loaded. MSO.DLL!03dd7398() Unknown No symbols loaded. [External Code] Annotated Frame Mso30win32client.dll!5c1f6595() Unknown No symbols loaded. Mso30win32client.dll!5c1f7249() Unknown No symbols loaded. MSACCESS.EXE!00a81aa5() Unknown No symbols loaded. ACECORE.DLL!19a289ab() Unknown No symbols loaded. MSACCESS.EXE!00d683b1() Unknown No symbols loaded. [External Code] Annotated Frame ACECORE.DLL!19b654ae() Unknown No symbols loaded. ACECORE.DLL!19a12e3f() Unknown No symbols loaded. ACECORE.DLL!19b654ae() Unknown No symbols loaded. ACECORE.DLL!19a29690() Unknown No symbols loaded. ACECORE.DLL!19a2955d() Unknown No symbols loaded. ACECORE.DLL!19a2a9ea() Unknown No symbols loaded. ACECORE.DLL!19a2a8b9() Unknown No symbols loaded. MSACCESS.EXE!009c3809() Unknown No symbols loaded. ACECORE.DLL!19a2dab4() Unknown No symbols loaded. MSACCESS.EXE!009c344f() Unknown No symbols loaded. MSACCESS.EXE!00a899d7() Unknown No symbols loaded. Mso40UIwin32client.dll!5b4c0b03() Unknown No symbols loaded. MSACCESS.EXE!009cef1c() Unknown No symbols loaded. Mso40UIwin32client.dll!5b4c0b03() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5d6c52() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5d6b98() Unknown No symbols loaded. Mso40UIwin32client.dll!5b4d476c() Unknown No symbols loaded. Mso40UIwin32client.dll!5b4d448a() Unknown No symbols loaded. Mso40UIwin32client.dll!5b4c09ad() Unknown No symbols loaded. Mso40UIwin32client.dll!5b4c09ad() Unknown No symbols loaded. [External Code] Annotated Frame Mso40UIwin32client.dll!5b5d6c52() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5d6b98() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5dad4b() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5db0dc() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5e17b8() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5df502() Unknown No symbols loaded. Mso40UIwin32client.dll!5b4a6c2c() Unknown No symbols loaded. Mso40UIwin32client.dll!5b5e499e() Unknown No symbols loaded. [External Code] Annotated Frame Med venlig hilsen Morten Høgholm Pedersen Mobile: +45 3054 5892 Email: ho...@gm... LinkedIn: mhpedersen Skype: m.h.pedersen -----Original Message----- From: Dimitry Sibiryakov [mailto:sd...@ib...] Sent: 2017-09-06 13:10 To: fir...@li... Subject: Re: [Firebird-odbc-devel] MS Access 2016 crashing when using two Firebird ODBCs 06.09.2017 13:06, hoegge wrote: > When I link tables from more databases on same > server Access crashes all the time. Did you look at call stack on crash? -- WBR, SD. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Dimitry S. <sd...@ib...> - 2017-09-06 11:09:38
|
06.09.2017 13:06, hoegge wrote: > When I link tables from more databases on same > server Access crashes all the time. Did you look at call stack on crash? -- WBR, SD. |
|
From: hoegge <ho...@gm...> - 2017-09-06 11:06:20
|
Hi I have the same problem. When I link tables from more databases on same server Access crashes all the time. I do not have the problem in Excel, though, where I can have several active connections at the same time. Unfortunately I do not have another SQL server to test against, with another ODBC driver, which would be the next natural thing to test. Have you tried that? kr Morten -- Sent from: http://firebird.1100200.n4.nabble.com/firebird-odbc-devel-f1284633.html |
|
From: Nick C. <ni...@yo...> - 2017-07-21 03:30:19
|
Hi all, I've been using MS Access to connect to Firebird ODBC for the last 12 years without an issue but recently I've started having a problem with Access crashing when connecting to databases via ODBC. I tried updating the ODBC drivers again and thought that that had fixed it, but it hasn't. The problem is that I want to connect to two different Firebird databases from within MS Access so that I can move data between them. The ODBC works fine as long as I only connect to one of them at a time; after opening a table from one source, MS Access crashes as soon as I try to open a table on the second connection. I tried creating a new MS Access database and added one table linked via ODBC from two FB databases and it still crashes when I open the second table so that rules out a corruption in my original MS Access database. We have not made any changes to Firebird on the server for 18 months. Microsoft have probably updated MS Access in this time (so that may be the root cause of my problems, but I have no way of knowing). I'm using MS Access 2016 on Windows 10 with Firebird_ODBC_2.0.5.156_x64 and Firebird 2.5.5 on the server. As the FB databases are located on our sever so I'm the databases in the ODBC are defined like this: 192.168.0.10:D:\Databases\Server\biscoTest\Database\BISCO.fdb. Any suggestions? Cheerio Nick --- This email has been checked for viruses by AVG. http://www.avg.com |
|
From: <me...@be...> - 2017-04-17 07:11:35
|
Hello. When compiling the version 2.0.4 (155) of OdbcJdbc for Linux (ArchLinux, package: https://aur.archlinux.org/packages/firebird-odbc/ ), a compilation error appears. AFAIK, it appears because GCC moved to the "C++11" standard, and the source code is not compatible with this standard. The source code includes macros for string literals that clash with the new C feature called "user-defined literals", see http://en.cppreference.com/w/cpp/language/user_literal . I am not familiar with this obscure feature, so I am not able to fix the source code. Instead, I give GCC a parameter to parse the source code with the old standard "C++03". I patched "OdbcJdbc/Builds/Gcc.lin/makefile.linux". IMO, the source code should be fixed in the near future. The error message: {{{ In file included from ../../IscDbc/IscDatabaseMetaData.cpp:47:0: ../../IscDbc/IscDatabaseMetaData.cpp: In member function ‘virtual const char* IscDbcLibrary::IscDatabaseMetaData::getDriverVersion()’: ../../IscDbc/../SetupAttributes.h:139:65: помилка: unable to find string literal operator ‘operator""buildnum’ with ‘const char [7]’, ‘long unsigned int’ arguments #define BUILD_DRIVER_VERSION(major,minor,buildnum) major"."minor"."buildnum ^ ../../IscDbc/../SetupAttributes.h:150:25: зауваження: in expansion of macro ‘BUILD_DRIVER_VERSION’ #define DRIVER_VERSION BUILD_DRIVER_VERSION( ZERO_MAJOR BUILD_STR2( MAJOR_VERSION ), ZERO_MINOR BUILD_STR2( MINOR_VERSION ), ZERO_BUILDNUM BUILD_STR2( BUILDNUM_VERSION ) ) ^~~~~~~~~~~~~~~~~~~~ ../../IscDbc/IscDatabaseMetaData.cpp:350:9: зауваження: in expansion of macro ‘DRIVER_VERSION’ return DRIVER_VERSION; ^~~~~~~~~~~~~~ make: *** [makefile.linux:127: Release_x86_64/obj/IscDatabaseMetaData.o] Помилка 1 }}} |
|
From: ML <d4t...@gm...> - 2016-11-17 11:25:20
|
*On 17/11/16 08:06, Dimitry Sibiryakov wrote:* > *17.11.2016 11:51, ML wrote: * >> It looks like the driver does not populate its database name >> attribute from the connection string. > According to MSDN, it must not. But it must return SQL_NO_DATA. > Register ticket in tracker, please. Well that's strange because FreeTDS does it. Did not test any other driver, though, just these two. But I guess ODBC is a little bit anarchic in these regards; the documentation itself says in several places "some drivers do this" or even "most drivers return that" or things like those; there seems not to exist a formal requirements list. Thanks a lot for your help, Dimitry, I will file the bug. -- zxMarce |
|
From: Dimitry S. <sd...@ib...> - 2016-11-17 11:07:05
|
17.11.2016 11:51, ML wrote: > It looks like the driver does not populate its database name attribute from the connection > string. According to MSDN, it must not. But it must return SQL_NO_DATA. Register ticket in tracker, please. -- WBR, SD. |
|
From: ML <d4t...@gm...> - 2016-11-17 10:51:34
|
*On 16/11/16 17:07, Dimitry Sibiryakov wrote:*
> *16.11.2016 20:32, d4t...@gm... wrote: *
>> I'm calling SQLGetConnectAttr() with the SQL_ATTR_CURRENT_CATALOG
>> attribute, but it does not seem to return anything meaningful.
> Do you check its return value? It must be SQL_NO_DATA if you didn't
> call SQLSetConnectAttr() beforehand.
I don't call SQLSetConnectAttr() before. Explanation below.
Actually, I'm calling SQLGetConnectAttr() twice: One to get the
necessary buffer (string) lenght. The second time is to actually
retrieve the string. None fails.
My code is this:
SQLRETURN retcode;
SQLINTEGER charsNeeded = 0;
char *dbName;
retcode = SQLGetConnectAttr(connHandle, SQL_ATTR_CURRENT_CATALOG,
NULL, (SQLINTEGER) 0, (SQLINTEGER *) &charsNeeded);
if (SQL_SUCCEEDED(retcode))
{
dbName = malloc(charsNeeded++); //Add one to get a buffer with a
trailing NULL
dbName[charsNeeded++] = 0; //Append NULL
retcode = SQLGetConnectAttr(connHandle,
SQL_ATTR_CURRENT_CATALOG, dbName, charsNeeded, &charsNeeded);
if (SQL_SUCCEEDED(retcode))
{
desc->name = GB.NewZeroString(dbName); //This creates a
Gambas string with a copy of the ODBC-retrieved string.
} else {
reportODBCError("SQLGetConnectAttr SQL_ATTR_CURRENT_CATALOG
(string)", connHandle, SQL_HANDLE_DBC);
}
} else {
reportODBCError("SQLGetConnectAttr SQL_ATTR_CURRENT_CATALOG
(len)", connHandle, SQL_HANDLE_DBC);
}
The calls do not actually fail (reportODBCError() is never called), and
the calls do fetch data, but it is not what I am looking for.
Also, I never call SQLSetConnectAttr() with SQL_ATTR_CURRENT_CATALOG, as
I am normally connecting with SQLDriverConnect(), directly passing a
connection string which includes the database name.
It looks like the driver does not populate its database name attribute
from the connection string. Just in case, the connstring I'm using is
"Driver=Firebird;DataSource=localhost;Port=3050;Database=localhost:/tmp/FBExample;UId=SYSDBA;Pwd=password;".
The routine to get the database name is called only when the component
connects to the DB successfully.
|
|
From: Dimitry S. <sd...@ib...> - 2016-11-16 20:08:11
|
16.11.2016 20:32, d4t...@gm... wrote: > I'm calling SQLGetConnectAttr() with the SQL_ATTR_CURRENT_CATALOG attribute, but it does > not seem to return anything meaningful. Do you check its return value? It must be SQL_NO_DATA if you didn't call SQLSetConnectAttr() beforehand. -- WBR, SD. |
|
From: <d4t...@gm...> - 2016-11-16 19:32:23
|
Hi there. Intro: I'm enhancing Gambas3 (a VisualBasic lookalike for Linux, "but not a clone!") ODBC component. It was kinda non-functional and still lacks functionality, but I got it to the point of being able to connect and retrieve data from MSSQL servers via unixODBC and FreeTDS. I also installed the ODBC driver for Firebird because a Gambas user noticed that the component was retrieving Firebird data incorrectly. The problem was fixed and the component now is up to par with MSSQL, except for one thing. The component populates a high level BASIC property with the Database name (this would be the Catalog name in MSSQL parlance). I cannot get this name correctly from Firebird. I'm calling SQLGetConnectAttr() with the SQL_ATTR_CURRENT_CATALOG attribute, but it does not seem to return anything meaningful. It usually returns a 2-char string, whose 2nd char is not printable, and the first one is normally a lowercase "L", but the database has no L's in its name. Since this is an ODBC-2 attribute I thought it should work. It certainly does under MSSQL. Is there anything I can do to get the DB/catalog name correctly? Thanks, zxMarce. |
|
From: Dimitry S. <sd...@ib...> - 2016-11-08 11:55:06
|
08.11.2016 12:50, gmi...@gm... wrote: > ? tcip/IP string ? what do you mean ? > it like \\192.168.1.1\sharedfolder\data\file.FDB ? It like is written in Firebird Quick Start Guide and Language Reference. -- WBR, SD. |
71 messages has been excluded from this view by a project administrator.
