No suitable driver found when making SQL connection to MS Access Database in java -


I have a simple Java application in Jebton (GateDataFormDB) which assumes loading data from the database shown in the path In the code given below, in Jtable in the application.

Edit in code: 

  Private Zero GetDataFromDBActionPerformed (java.awt.event.ActionEvent evt) {Connection Con; Results set rs = null; Description stmt; Try {class.forName ("sun.jdbc.odbc.JdbcOdbcDriver"); Con = DriverManager.getConnection ("jdbc: odbc: driver = {MS Access driver (* .mdb, * .accdb)} dbQ = c: \\ user \\ Bruger \\ document \ database11.accdb"); Stmt = con.createStatement (); String query = null; Query = "select * with cost"; Rs = stmt.executeQuery (query); I = 0; While (rsnext ()) {i = i + 1; JTable.getModel () SetValueAt (rs.getString (1), i, 1); JTable.getModel () SetValueAt (rs.getString (2), i, 2); } Rs.close (); Stmt.close (); con.close (); } Hold (exception mistake) {System.out.println (err.getMessage ()); }}   
 When I press the button I get the following message in the Run Output window:  
  No suitable driver was found for jdbc: odbc: driver = {Microsoft Access Drivers ( .mdb,  .accdb}}; DBQ = C: \ Users \ Bourgeois Documents \ database11.acadb   
 I have the top Import of my code:  
  import java.sql. *;   
 I change from "Microsoft Access Driver" to "MS Access Driver" Also tried, but I get the same message in the Run Output window.  
  Jdbc: odbc: driver = {MS Access driver ( .mdb,  .accdb }} DBQ = C: \ Users \ Bruger \ Documents \ Database11.accdb  No suitable driver was found  
 I am truly grateful for all your help, input and feedback.   
 
 
 dependent driver and if you are first JDK6 **!  
 The driver must be registered.  
 Try adding Switch to:  
  Class.forName ( "sun.jdbc.odbc.JdbcOdbcDriver");   
 Such:  
  class. ForName ("sun.jdbc.odbc.JdbcOdbcDriver"); Con = DriverManager.getConnection ("jdbc: odbc: driver = {Microsoft Access driver (* .mdb, * .accdb)}; dbQ = c: \\ user \\ Bruger \\ document \ database11.accdb");   
 It is also worth mentioning that whenever you get a connection, you do not have to do this, just once to ensure that the class is full.  
 There are a few stackwaveflow questions about this, but the reason for this is:  
 Source - From Java Tutorials:  
 
 In previous versions of JDBC To get a connection, you have to initialize your JDBC driver to call the class for the first time. ForName These methods require java.sql.Driver of a type of item. Each JDBC driver has one or more squares which implements the interface java.sql.Driver. ... Any JDBC 4.0 drivers that are found in your class path are automatically loaded. (However, with the standard class to load any driver manually before you JDBC 4.0.)   
 
 On the related and very important note.  
 I will also suggest how to handle the connection. If you are not familiar with them then external resources such as database connection and cursor are easy to leak. 'Try the blocks at the end', or see 'efforts-in-resources' in Java 7+ recently.

Comments

Post a Comment

Popular posts from this blog

Java - Error: no suitable method found for add(int, java.lang.String) -

I'm in the middle of homework work and I'm stuck. At this point in my code, I think that I should have a GUI window that opens and allows me to type "inserted text number". Notice is not going anywhere but at this point, If I pass through the problem then it will be in a linked list. I am getting two of the same error for the lines. Add (index, element); And I can not seem to get past it, there is no suitable method for the error "add (int, java. string string)". Code is below, please advise. To clarify - this will not be a method error because it is a linked list. There should not be any way involved. import java.awt. *; Import java.awt.event. *; Import javax.swing. *; Import java.util. *; Import java.util.Scanner; Import java.util.LinkedList; Public class TopTenList JFrame {Private TopTenList tt; See the Private JTextArea list; Private JTextField cmdTextField; Private JTextField resultsTestfield; // This GUI window is the code for the public toptist...
Read more

java - JPA TypedQuery: Parameter value element did not match expected type -

I am using JPA 2.0 and getting the following code in the DAO layer: Public Zero Test () {string key = "status"; String [] Conditions = {"A", "B"}; & Lt; TestTable & gt; Results = Search (Keys, Conditions); } Public listing & lt; TestTable & gt; Search (string key, object value error) {string sql = "test ndf to testlet and jade nand." + Key + "in:" + key; TypedQuery & LT; TestTable & gt; Query = entityManager.createQuery (SQL, TestTable.class); Query.setParameter (key, Arrays.asList (valueArr)) / *** Error Line *** Return query.getResultList (); } In the above error line, it throws the following exception: java.lang.IllegalArgumentException: parameter value element [[Ljava.lang.String; @ cbe5bc] did not match the expected type [java.lang.String] Why is this expected type string while actually this string []? Please help! Note: This is derived from the normal routine and is a simplified code. I can no...
Read more

c++ - static template member variable has internal linkage but is not defined -

Yes, I know, there is a question with almost the same title, but it refers to a different situation. Error message) In my case, I have a .cpp file with a big named designation name (implementation details). There is a property class template with a static data member in that name space, which I need to access from outside the unknown namespace. I give it a little bit of meat: file.hpp namespace Bar {template & lt; Typename A & gt; Struct foo {static_assert (is_same & lt; a, float & gt; :: value} is_same & lt; a, double>: value, ""); Fixed zero set_static_var (a const & x); // ...}; } and file.cpp namespace {template & lt; Typename A & gt; Struct foo_traits {// supports the implementation of several static code bars: foo & lt; & Gt; Fixed A data; }; The template's & lt; & Gt; Float foo_traits & lt; Float & gt; :: datum; // No change if this is in the global namespace template & lt; & Gt; Doub...
Read more