Any idea of better names? I can only think of renaming Net to Network. And I
don't think this would help an user who doesn't know about the difference
between the network and embedded driver in Derby to select the right one. What
could help such an user is not registering the embedded driver at all. But this
would cripple the IDE for users who know what they are doing...

Re telling the user to user another driver: I would suggest just adding a
generic message like "If you are using a network driver, check that the database
server is running and that you are using the right driver. If you are using an
embedded driver, try using the corresponding network driver (if any) instead."
to the error dialog box.

Please explain what is the difference between them and I would try to come up with UI improvements. 
Thanks.

(We renamed Derby to Java DB in NetBeans, I will use the latter name.)

Java DB (Embedded) is an embedded driver, that is, it connects to a database
inside the JVM the driver is running in. It doesn't connect to a network server.
Instead, the "server" is the driver itself (that's why no network connection is
needed). This is usually not what the user wants (at least not during
development), because the database can be accessed only from a single JVM. Thus
it can't be accessed e.g. from NetBeans and an application server at the same time.

Java DB (Net) is a network driver, that is, it connects to a network server
which is listening on some IP address and socket. Since the server manages the
database, the database can be accessed from multiple JVMs (even on remote
computers).

After discussion with Andrei we suggest to:

- make a small change in the name of the driver to "Java DB (Network)"
- make this driver initially selected in the New Connection Database dialog instead of JDBC-ODBC 
bridge. I believe this would fix the original finding in the study. The question is whether it is the right 
step as probably the JDBC-ODBC driver is more commonly used.

Pavle, Petre do you have a strong opinion about it?

BTW, Andrei please change the name of the action on Databases node from "Add Connection..." to "New 
Connection...". We're consistently using New Connection on other places and the dialog title bar is "New 
Database Connection". Thanks.

ok with me

Re. "Add Connection..." -> "New Connection...". "Add" is consistent with "Add
Driver/Table/Column/Index" on other DB Explorer nodes. Should these action be
renamed too?

Re. Should these action be renamed too?

Maybe yes. The guideline we're using for distinguishing Add and New is something like:
- Use Add if adding from existing set of values. Typically from a file chooser, or a list of values. When 
using Add, use Remove as the opposite action.
- Use New when creating something new - specifying it's values like name, content, etc. When using New, 
use Delete as the opposite action.

Sometimes it's a bit hard to make choose the right one. I think for connection, the user is creating new 
connection more than adding from existing connections.

Re. actions rename: OK. I reopened issue 74713.

Fixed.

Checking in derby/src/org/netbeans/modules/derby/DerbyOptions.java;
/cvs/db/derby/src/org/netbeans/modules/derby/DerbyOptions.java,v  <-- 
DerbyOptions.java
new revision: 1.5.2.2.2.7; previous revision: 1.5.2.2.2.6
done
Checking in
src/org/netbeans/modules/db/explorer/actions/ConnectUsingDriverAction.java;
/cvs/db/src/org/netbeans/modules/db/explorer/actions/ConnectUsingDriverAction.java,v
 <--  ConnectUsingDriverAction.javanew revision: 1.28.2.1.2.3; previous
revision: 1.28.2.1.2.2
done
Checking in src/org/netbeans/modules/db/util/DriverListUtil.java;
/cvs/db/src/org/netbeans/modules/db/util/DriverListUtil.java,v  <-- 
DriverListUtil.java
new revision: 1.9.2.2.2.4; previous revision: 1.9.2.2.2.3
done

v.