What format do I use to store a relatively small amount of user data

I am writing a small program for our local high school (pro bono). The program has an interface allows the user to enter school holidays. This is a simple stand alone Windows app.

What format should I use to store the data? A big relational data is obviously overkill.

My initial plan was to store the data in an XML file. Co-workers have been suggesting that I use JSON files, Access Databases, SQL Lite, and SQL Server Express. There was even a开发者_JAVA技巧 suggestion of old school INI files.

Projects like this have a habit of getting bigger, quickly, and if they do your XML file will become complex and a burden to manage.

I would not recommend storing the data in an xml file or json - they are just text files by a different name, all suffering from the same problem - you don't have any control over who edits them.

Use some kind of db, starting from the small ones first (Access, SQLLite)

Edit

Based on your latest comments, roll forward to a point where the users have been using the app for two years.

• How much data do you expect to have stored by then?
• Will the user(s) need to look back through historic data to see, for example, what they did this time last year

And more so, right now

• What is Teacher A doing on Thursday afternoon
• Will Teacher B be free to attend event on 15th May 2010?
• Can Student C attend event D?

All of these questions/problems are a lot easier/more efficient to handle with SQL. Plus your resulting codebase will make a lot more sense. Traversing XML isn't the prettiest of things to do.

Plus if your user base is familiar with Excel already, linking Excel to a SQL database (and produce custom results) is a lot easier than doing the same with XML.

Have you considered using SQLite? It'll result in a small .s3db file. SQLite is used by all kinds of desktop applications for local storage.

There's a SQLite .NET library that'll allow you to use ADO.NET to CRUD your data.

Check out Mike Duncan's article on how to get started with SQLite in .NET.

I would have to second the Json answer and SQL Lite.

Another option would be to use the built in database that's included in all of windows (since Windows 2000), ESENT. There is a codeplex project to make it easy to work with http://managedesent.codeplex.com/

Hm, obviously SQL Express is a full blown database - otohj it may make sense. Why NOT use a databsae if they already have one ?;)

Otherwise I would possibly go with a XML file.

I would recommend an XML file and a typed dataset.
You will need to figure out where to put the XML file.

Note that if you ever want to allow multiple users to use it, you need to use a database, such as Access or SQL Server.

I'd go for

• SQL Server Express (free and full blown relational database)
• XML/JSON if you don't want a database (LINQ to XML might be a big help here).

xml files seems to be a good option. using Linq to xml it should be quite easy to read/write the files from objects/to objects. check out XDocument and XElement classes Access Databases, SQL Lite, and SQL Server Express seens like an overkill. do you really need a database to store a simple calendar data? is your application going to grow?

From "simple stand alone Windows app" it sounds to me like it's not critical. I'd go with whatever is easiest, or what you are most comfortable with. XML is usefully human readable, but a sensibly formatted flat file might be just as sensible.

I'd use serialized classes.

One thing to consider if you use a database instead of a text file of some sort: you're no longer a "simple stand alone Windows app". Now you've (most likely) got an installation program to write.