Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Design Suggestions

Ranch Hand
Posts: 15304
Mac OS X IntelliJ IDE Chrome
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am creating an applet based Help Desk Tracking system for my department. I have a Web Server where I will be hosting the applet and will also maintain the Database on the Web Server.
The Database must be able to be accessed from anywhere inside my company. Therefore I need to be able to access it via UNC or IP through the ODBC.
I would prefer to use an SQL database, prefereably MySQL.
I also want to keep this project as much JAVA as possible. Meaning no XML, CGI, etc.
My initial plan was to use JDBC to connect to an MS Access DB through the ODBC but this failed because Access is a client/client database and I need a Server/Client database.
I know how to use the JDBC API so that is not a problem.
I would appreciate any hints, ideas, suggestions for this project.
Should I use RMI instead of JDBC and keep the DB manipulation completely local to the Server or is JDBC the way to go on this.
Also, if anyone knows how to Register MySQL as a Server with the system so that is shows up in the available Servers list in the ODBC, that would be grealty appreciated as well.
Thanks for any help.
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You might want to consider keeping all of the database access code on the middle, or server tier. This way it will be self contained and should be easier to administer and maintain.
You could communicate with your server using RMI. I'm not sure I understand your question about RMI vs JDBC. Even if you use RMI you will still need JDBC to communicate with your DB, so it doesn't seem like an 'either/or' situation, but maybe I'm missing something.
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at .
We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please re-register and select a new name which meets the requirements.
My, my, aren't you a big fella. Here, have a tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic