Everything has got its own deadline including one's EGO!
[CodeBarn] [Java Concepts-easily] [Corey's articles] [SCJP-SUN] [Servlet Examples] [Java Beginners FAQ] [Sun-Java Tutorials] [Java Coding Guidelines]
Read about me at frankcarver.me ~ LinkedIn ~ Frank's PhD research
Originally posted by Frank Carver:
Does that make sense?
a text file in something such as CSV or TSV
a properties file where the property names encode column and row (such as name_1 = Frank)
something like a hashMap in memory, saved/loaded using Java serialization
Read about me at frankcarver.me ~ LinkedIn ~ Frank's PhD research
Originally posted by Frank Carver:
as it's not convenient to edit the data for non-developer
Ah. Do you anticipate that non-developers will need to edit this datafile then?
From your description above I inferred that the data file would be created once then loaded and used many times by the application, so the choice of format was driven mainly by simple and robust coding. If you have other requirements of this format, then maybe we need to explore the range of choices a bit further.
Can you describe in a bit more detail how you expect the stored form of the data will be created and used during normal work processes.
Originally posted by ankur rathi:
If I keep data in excel sheet only then editing would be, much, much easy for user as everyone know excel sheets. But how good it is from efficiency point of view?
[ May 23, 2007: Message edited by: ankur rathi ]
Read about me at frankcarver.me ~ LinkedIn ~ Frank's PhD research
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Originally posted by Frank Carver:
The key thing I notice from your description is the workflow. It seems that anyone (or at least anyone authorized) can change and re-save the Excel file at any time.
If that is the case, there is no reason why your application can not transfer the information from an Excel file to something more efficient for your processing whenever it notices that the file has changed. Then you can have the usability benefits of Excel, and the performance and easy coding benefits of a database or an in-memory table.
I'm still slightly puzzled as to why you are not considering building an editing UI. Even if you don't fancy a Java solution, then why not a simple Access application. An app to provide friendly editing of a single DB table shouldn't take more than half an hour to set up.
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |