Jason writes:

As of today, basic SQL functionalities and related triggers are complete.
Also, concrete design on user interface has been implemented and related triggers are connected to relevant controls, as well as inter-connectedness of the forms.

Forms are connected in a following manner:

Few Issues arose in implementation of SQL Functions. Two of the important ones are:

1. SQL CE did not support simple change column command within ALTER TABLE.
2. Way of forwarding information between forms (eg/ from ViewAll to View Details)

Frankly, there was a work-around for both.

1. It is a little more work, but possible with a temporary extra storage.
   => create a new column, copy from old column, drop old column

2. Since Date and Subject combinations are unique, pass on that information to next form and in the next form, do another query on the date, subject combination.

Now, since database related functions are approaching the finalization, actual database file handling and import/export issues must be addressed.

While database file handling (names of database, etc) is an easy job in terms of implementation, it is a tricky job to come up with an easy and interactive interface. (and SMART.)

The bigger issue now would be the Import/Export feature.

To make it more compatible with various other platforms, I am planning to export as an XML file and a .sql file.

Basically, XML file would hold all the data in XML form, while sql file would simply have relevant sql commands to create relevant tables.

Export should not be too big an issue, but import is a little harder job. Also, restrictions should apply that the default field names must be retained and types of additional fields are restricted to nvarchar, integers, and numbers as the Journal Manager would not support other types for additional fields.

It has been suggested to include a media (i.e. pictures, inks, etc) and although it would be great, the import/export will likely to not include those as exported files are simply text files. More importantly, it will be hard to incorporate these types of data in SQL, the feature will not be likely to be implemented in this version of Journal Manager.

Jason