ansaurus

Question

JDBC ODBC.. (Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException)

Answer 1

+3 A:

EDIT: You still haven't indicated which is line 197 in the question, but I'll assume it's

p1 = conn.prepareStatement(s1);

This is almost certainly due to this bit of the constructor:

Connection conn=DriverManager.getConnection("jdbc:odbc:reg","system","suganthi");

This declares a local variable called conn. Presumably you also have an instance variable called conn, but the local variable is hiding it. You're assigning to the local variable, which means the instance variable is going to keep its default value of null. You probably meant just:

conn = DriverManager.getConnection("jdbc:odbc:reg","system","suganthi");

However, if an exception occurs you shouldn't just print "Error" and keep going... you should probably throw an exception from the constructor instead. After all, the instance isn't going to behave properly unless you've got a database connection.

You should also consider only creating a database connection when you actually need it, and closing it immediately afterwards. Use a connection pool to allow this to be efficient where appropriate.

Original answer

You haven't shown the bit of code which is throwing the exception - namely jButton1ActionPerformed, with line 197 being the culprit. You've shown us jButton3ActionPerformed instead.

Show us the right piece of code, with line numbers, and we're more likely to have a chance to help you. Or just look at what's being used on line 197 - something there is resulting in a null reference which you're trying to dereference, e.g.

int foo = someNullValue.getIntValue();

It may be the result of a method call though, e.g.

foo().getIntValue(); // Will throw if `foo()` returns null

As an aside, doing database work in the UI thread isn't generally a good idea - although as you're a beginner it may be simpler to get that right and live with the UI hanging during database access than getting multithreading right. You should consider threading it properly at a later date though, when you have more experience.

Jon Skeet 2010-04-03 11:01:55

private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) { PreparedStatement p1;try {System.out.println("works");String s1="insert into reg(num,name) values(?,?)";p1 = conn.prepareStatement(s1);// line 197JOptionPane.showMessageDialog(this, "Statement prepared");p1.setString(1,num.getText());p1.setString(2, name.getText());p1.executeUpdate();}catch (SQLException ex) {Logger.getLogger(sample.class.getName()).log(Level.SEVERE, null, ex); } } both jbutton1 and jbutton2 do the same task. So copied code by mistake.

enthudrives 2010-04-03 11:24:14

@enthudrives: Please edit your question rather than putting code in a comment. It's basically unreadable in a comment.

Jon Skeet 2010-04-03 11:29:10

ok. I edited the question..

enthudrives 2010-04-03 11:32:04

Answer 2

A:

the exception form jButton1ActionPerformed function not in jButton3ActionPerformed ,

make sure that Connection object have value and you already connected to data base.

Wajdy Essam 2010-04-03 11:04:01

public sample() { initComponents(); try { Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); } catch(ClassNotFoundException ex) { JOptionPane.showMessageDialog(this, "Error!"); } try { Connection conn=DriverManager.getConnection("jdbc:odbc:reg","system","passwd"); if(conn!=null) JOptionPane.showMessageDialog(this, "Connected!"); } catch(SQLException ex) { System.out.println("Error"); } }My connection is established

enthudrives 2010-04-03 11:27:01

your connection is defined inside constructorwhen constructor end then your reference is out of lifeso define Connection outside constructor

Wajdy Essam 2010-04-03 11:54:37

Yippee.. it works :) Thanks a lot :)

enthudrives 2010-04-03 12:33:44

ansaurus

tags:

views:

answers:

JDBC ODBC.. (Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException)

related questions