tags:

views:

322

answers:

1

Hello,

I am developing a java app (with odbc bridge - forgive me - the only paradox driver I have been able to obtain is the microsoft odbc driver) - which works fine while in eclipse, (and netbeans) - connecting and obtaining data from an ancient paradox 5.x database. So long as it is run from inside my IDE - it compiles and runs flawlessly.

When I export it to a runable jar, suddenly [code][Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified[/code] occurs.

The jar is being run on the same box as my developing IDE - so I am confused about the cause. It is being run via console from a user account, as per the IDE.

My connection string is "jdbc:odbc:Driver={Microsoft Paradox Driver (*.db )};DriverID=538; Fil=Paradox 5.X; DefaultDir=C:\paradox\database\location\" - obtained from connectionstrings.com - and as mentioned before, working fine while run from the IDE.

The above seems to 'magically' create its own connection, avoiding the setup of a dsn - I am unsure quite how it does - but it works.

The only other thing I can think that might be pertinent is that my PC is a 64bit o/s (windows server 2008).

Please help, any suggestions or comments will be greatly appreciated.

Thanks, Matt

A: 

Work around obtained - my JRE for developer was 1.6.0_07, while my JRE for O/S was set to 1.6.0_09.

Although I have no idea why one has access to my driver, and the other doesn't - I can set my JRE to the successful one - but I would still like to know why / how the drivers each version supports are different - and how I can make it work on all.

matt