FInally, I think this post will answer my question. I'm thinking of later on
down the road converting an Access database I created with a VB interface to
one done in Java. I've been searching all over for info, but I've seen
nothing in reference to Access. At this time, all I would to know would it
be similar to connecting as in VB and would the JDBC bridge work similar to
it, would I have to use an IDE other than Visual J++ to create the
interface? This would be my first time doing this and the database is being
used in the division of a small college I work for. Because of the
environment and the amount of data going into it, there isn't a need for a
large capacity DBMS.
> FInally, I think this post will answer my question. I'm thinking of later on
> down the road converting an Access database I created with a VB interface to
[quoted text clipped - 6 lines]
> environment and the amount of data going into it, there isn't a need for a
> large capacity DBMS.
Let me answer this in pieces.
Microsoft provides an ODBC driver for Access. It only can be used on Windows. Therefore,
it is platform-specific. There is no JDBC driver for Access.
In Java, you can use databases which provide only ODBC drivers through the JDBC-ODBC
bridge. Sun includes a JDBC-ODBC bridge with their standard distro, but they warn that
it is not intended for production use. I'm not sure that matters since I don't think the
Access is suitable for production use, either ;^) There are some commercially available
JDBC-ODBC bridges, but I have no experience with them.
So, you can use JDBC in Java to use Access. You don't need an IDE. Is it similar to VB?
Using JDBC in Java would be similar to using ODBC in VB ... actually quite easier. If
you're looking for an interface more high level than that, you may need an IDE or some
other interface layer on top of JDBC. I don't have any recommendations on that.
In general, you can create an application using JDBC that can utilize different back-end
databases. However, there are a number of complications, such as, significant
differences in SQL syntax. Most pay only lip service to Standard SQL. Solid guidelines
on surmounting these obstacles are rare to non-existent.
For other aspects of your questions, I would repeat the suggestions I made previously.

Signature
Lee Fesperman, FirstSQL, Inc. (http://www.firstsql.com)
==============================================================
* The Ultimate DBMS is here!
* FirstSQL/J Object/Relational DBMS (http://www.firstsql.com)
R.A.J. - 06 Jun 2004 08:56 GMT
"> In Java, you can use databases which provide only ODBC drivers through
the JDBC-ODBC
> bridge. Sun includes a JDBC-ODBC bridge with their standard distro, but they warn that
> it is not intended for production use. I'm not sure that matters since I don't think the
> Access is suitable for production use, either ;^) There are some commercially available
> JDBC-ODBC bridges, but I have no experience with them."
That works out for me. I have the current version of the Java SDK. It's only
going to be used on Windows platform, so there's no need for it to be
neutral.
"
> So, you can use JDBC in Java to use Access. You don't need an IDE. Is it similar to VB?
> Using JDBC in Java would be similar to using ODBC in VB ... actually quite easier. If
> you're looking for an interface more high level than that, you may need an IDE or some
> other interface layer on top of JDBC. I don't have any recommendations on that."
This answers another important question---whether it would be similar to
working in VB. At the outset, just going over things, I thought that it
would be much easier in Java as well, but when I started reading about the
JDBC driver, it had getting second thoughts.
"> In general, you can create an application using JDBC that can utilize
different back-end
> databases. However, there are a number of complications, such as, significant
> differences in SQL syntax. Most pay only lip service to Standard SQL. Solid guidelines
> on surmounting these obstacles are rare to non-existent."
SInce SQL isn't a factor, I won't worry about it. And the fact of me having
to relearn SQL again is a reason.
Thank you for your help.
> > FInally, I think this post will answer my question. I'm thinking of later on
> > down the road converting an Access database I created with a VB interface to
[quoted text clipped - 29 lines]
>
> For other aspects of your questions, I would repeat the suggestions I made previously.