This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I know it is not required by the assignment specs, but would it be a good idea to allow the user to add records to a brand new database file? What I mean is this:
1) The user launches the client in standalone mode. 2) A "choose database file" dialog appears in front of the empty client window. 3) The user does not choose a database file and cancels the dialog. 4) The user is left with an empty client not showing any data. The user can do nothing except add new records. 5) The user selects to add a new record and is prompted by another dialog to either choose an existing database file or create a new one. If they choose to create a new one, they must supply a new database file name.
Seems like a lot of trouble to provide additional functionality for. The other consideration I am leaning towards is to just prompt the user with a "choose database file" dialog upon client startup. If the user cancels that dialog, then they cannot do anything (all functionality is disabled or warning popups appear when an action occurs) until they choose an existing database file from the File menu.
But make sure when you submit your assignment you bundle original database file otherwise automatically fail...
SCJP, SCWCD, SCBCD, SCJD, BB Java2 and JSP1.1
Joined: Apr 19, 2005
Ofcourse, you must package the original database file with your jar for submission. But do we need to be concerned about the user adding records to a new database file that the user would create? I'm leaning towards not allowing this as it says nothing in the specs about this, but I'm not totally sure.