Do I really need SQL for this?

[CelticDragon]

Hi guys...

Some of you may notice that I have been posting a lot recently about sql stuff as I just have always been unable to get my head around databases!

I'm not actually sure I need to use SQL for this current project, I need to get people to answer a load of questions - one user per application - and output a file that can be printed or emailed! I'm thinking that the user can get the app, use it and each answer can be put into a text file (or other extension) on their machine in a specific folder. I can then get these files and replace strings of text like X_Answer_1, X_Answer_2 in a html document and presto... the user can either save it to a location of their choosing or they can print it out...

The thing is that people will have to be able to take breaks from the questions to actively go out and find out some of them so some things would be saved and others not.... Does this make sense?

If it does, should I still try to use SQL?

[Corey]

There's a few main advantages to using databases, particularly having the ability to abstract or analyze aggregated data with very little effort. Other advantages include automated reporting, tracking, backup, etc. In general databases are a great way to deal with data. Once you get going with your first basic database you will find that they're not too bad to deal with, although I recommend interfacing with a MySQL database from your AMS app (over SQLite) if security is a priority.

If you definitely will "never need your data again" after the first usage then a database is probaby not neccesary. A lot of people end up in "data overload" this way. Definitely it's just as important for effective data management to know which bits to throw out as which ones to keep.

Another point of consideration, and I haven't touched on about a zillion others, is that a database can provide you with some level of legal insurance. It makes it easy to step back to any point in time and verify specific data. That can be invaluable in certain scenarios. When in doubt, it's probably safer, in general, to go with a database than without one, especially in regards to any sort of transaction related applications such as shopping carts, exams, or license agreements...

[TJ_Tigger]

SQL might be one of the more effecient ways to do what it is you want to do. The Quiz app that I built did not use it so it is deffinately doable.

Tigg