Menu
▾
▴
firebird-odbc-devel
|
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: 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: 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: 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: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: 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: 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: 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: 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-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: 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-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 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X