Please edit your post and REMOVE the personal information - that is NOT appropriate for the forum.
That is a pretty old version. There have been MANY bugs and enhancements since that version was released.
I suggest that you update to the current version of Sql Developer and then repost your question if you have the issue with the new version.
MOD: email address removed
Upgraded to v4.0.3 for win7-64, supposedly with jdk 7. But I have jdk 8, and it isn't clear to me where or how to switch to jdk 7 -- because apparently java 8 does not have an odbc bridge, per Jeff Smith.
My specific error:
Specified driver could not be loaded due to system error 126: The specified module could not be found. (Microsoft Access Driver(*.mdb), C:\WINDOWS\system32\odbcjt32.dll).
FWIW, I have odbcjt32.dll in C:\WINDOWS\sysWOW64
As Jeff notes in the other discussion you commented on:
you need to find out why the dll is not found, perhaps due to some 32-bit versus 64-bit mismatch in your installation environment.
Otherwise, for your Java JDK concerns...
- Use the Help > About > Properties tab, enter java.version in the the Search widget to see which java SQL Developer thinks it is using.
- For 4.0.3, control the java version via SetJavaHome in product.conf in C:\Users\<yourUserID>\AppData\Roaming\sqldeveloper\126.96.36.199.0, where Windows treats AppData as a hidden directory.
Help / About has java.version 1.7.0_55
C:\Users\<me>\AppData\Roaming\SQL Developer has folders:
188.8.131.52.0 does not exist. No product.conf in the system4... folder.
Googling for info on odbc dll's.
There will be
- C:\Users\<me>\AppData\Roaming\SQL Developer\
Look in the second directory structure for product.conf.
Ok. Oops. I missed that 2nd folder (Roaming\sqldeveloper). Of course, SD403 sees the jdk7 anyway, so that's a moot issue at this point.
The picture I'm seeing in regard to ODBC is this:
64-bit SQL Developer must be using 64-bit ODBC by default, and presumably not configurable.
I am using AccessXP (Access2002), even though my PC is a 64-bit Windows7 machine.
AccessXP is 32-bit software; it does not have a 64-bit odbc driver.
Unless 64-bit SQL Developer 403 can be configured to use 32-bit ODBC drivers, I will have to try running 32-bit SD.
Since the 64/32-bit version of SD403 does not include a jre, I may resolve the odbc issue and find a new java issue. Since jdk7 was included in the 64-bit download, do you know if that jdk can be installed more directly into the Windows environment? For example, by simply copying folders from sqldeveloper to \Program Files\Java, or \Program Files (x86)\Java\? Or, does SD403/64-32 work with \Program Files (x86)\Java\jre6?
you want to run sqldev as a 32 bit app, get a 32 bit jdk then edit your product.conf file to point to that new java home
no JRE - has to be a JDK
Just as you can install as many SQL Developer versions as desired, multiple (32-bit and/or 64-bit) JDK installations are fine. Get what you need from
and during the install process you can skip the public JRE installation. All you need is the JDK, then update the product.conf SetJavaHome line.
Still no joy. The 32/64 version is the same build (184.108.40.206.84) as the 64-bit version, so it still uses 64-bit ODBC and gives the error 126 (odbcjt32.dll not found). Even when run with WindowsXP compatibility, the error is the same.
I don't think I can run SD403 as a 32-bit app; I think I need to run a 32-bit SQL Developer. I'm not sure where I downloaded v2.1.1 last week, but maybe I can find it and look for something between 2.1 and 4.0 - unless you have another suggestion. Thanks!
there's no such thing as a 32 bit sql developer - the code is the code. The JDK defines the bit level.
I was coming to the same conclusion.
So apparently it's jdk7 that does not use 32-bit odbc.
I'm downloading a v6 jdk, and we'll see how that goes.
Comparing the 32-bit (the i586 one ) vs 64-bit (the x64 one) versions of JDK 1.7, we see the JdbcOdbc.dll size on disk changes from 48KB to 64KB. So just make sure you have the 32-bit JDK installed and update product.conf to point to it. You may also wish to verify your PATH environment variable does not contain references to some other 64-bit JDK.
Also, when you update product.conf, keep in mind that on Windows 64-bit versions...
32-bit code installs into C:\Program Files (x86)\
64-bit code installs into C:\Program Files\
Perhaps you are already aware of that, but I just want to be sure. So many ways to get tripped...
What's past is prologue. Or something.
I've acquired an older, 32-bit Windows 7 PC and loaded SQL Developer 4.0.3 and JDK 1.7.55 on it. Now I can create a connection to the Access database. Technically, this resolves the issue in the original post.
Now I am working through the Migration wizard in SQLD. I get to the Source Database step and see a dropdown for Connection, to "Choose the Third Party Database from which you are migrating." Can you guess that the Access connection I just created is not there? (And no others, but that's the only TPD in the SQLDev environment.)
Should we continue this discussion on a new thread? Thanks!