Java Programming

I am developing a Java Standalone Application [Client] program that presently saves its data in HDD files. Each file contains data entered into a set of Data Entry forms. The Application produces a group of Reports as a function of the HDD data.

Soon I will offer my Application End Users a service where the data in the HDD files shall be saved on my server. My server provider provides a MySQL data base. Each client data set shall be a MySQL table with the table name being the End Users encrypted EMail address. The same reports produced by the Client shall be available from the Server via a Web Browser.

I plan to convert the client software to use a Data Base in lieu of the HDD files. The current thought is to use MySQL on the client side with a table for each current HDD file and a "Control" table for the Java Application "System" data.

I have just updated the Java Standalone Application from JDK 1.4.2 to JDK 1.5.0. I am doing the development on a Win XP platform and the testing on both the XP node and on a Mac OS X G4 Powerbook. I have purchased the new Panther Mac OS X which I believe will have the Mac 1.5.0 JDK. I presently use Eclipse 3.1.2 on each node.

I have read up on the "Java DB" and I like the embedded concept and it seems to have all the functionality I will need. My server provider has Java DB 10.2.2 installed currently.

Ideally I could implement my "Reports Writer" by interfacing with a Java DB object on both the Client and Server sides. On the Client and Server sides I plan to use the End Users Browser to display and print the Reports.

I would use the Server side MySQL data base to contain a KEY, Java DB object ordered pair. The KEY is the afore mentioned encrypted EMail address. The Application End User would sign into my server using any Internet aware web browser. After authorization, I would fetch the Java DB object and produce the requested Reports accordingly. Kinda like a Web Service but I do not think it fits the Web Service definition completely.

Finally some questions:
1)
Does the above system make sense or should I implement MySQL on both the Client and Server sides as I originally intended?

2)
I believe with the above system that I would need to include the Java DB Jar in my deployment process. If I go with the full MySQL approach what deployment problems do I create?

3)
I do not plan to go to JDK 1.6.0 because I am leery about it's availability on my Mac node.
From what i read so far on Java DB, I can download it and implement it using JDK 1.5.0.
Is that a correct assumption?

Thanks,
Jim...