I'm on a fence on this. Maybe you all can help me to decide on which direction to head in. I'm setting up some forms for my site. Right now I have the form saving the information to a mySQL DB. Works like a charm. I can go into my site's cPanel and use phpMyAdmin to view the information, bit of a pain, but I have not yet been looking for a php solution to that. I know just enough about php to be dangerous!
I could set it to CSV instead and just download the file and view it in OpenOffice, but again that seems to be a bit of a pain as well.
So I guess I'm just really curious as to what those of you who use WFB do with the information, mySQL and a php solution or CSV and a spreadsheet solution?

Stick with MySQL. (My personal opinion) Google for, and download, SQL Manager Lite. It's free. Lets you view your database without jumping through hoops. Well, once you get it set up anyway

My vote is for Mysql as you can export the table as a csv in a click of the mouse at your cpanel. I'm working on a PHP script at this moment that will export your table to csv so you can use a link to download it. I know Prism likes the straight csv approach. The only problem I've had is remembering not to delete the darn thing if I delete the form directory.

I do not have an issue with MySQL, it is just if I create an application that includes data manipulation I do not need to get someones database set up tables created. I can upload the database controls as well.

csv files are similar to a MySQL DB and have some advantages, they can easily copied, split in to other data sets and easily manipulated. I have auto created csv files to check handling times and they cn hold or reference any form of data. An image is referenced not stored in the DB for instance.

I hear you. A good practice is to grab a copy at the beginning of a script and work on that. Bring the copy to a common location and change the name and separator at the same time. I like to use the Pipe "|" easy to read compared to a comma.
Also bringing a copy to the root of the domain cuts out public_html/form/storage/csv/results.csv becomes results.csv less typing less problems.

Yup, I agree the easiest approach for appealing to a lot of users would be the csv approach. Keep all the files needed readily accessible and directly published and up and running at a click of a mouse. I would also suggest that any csv file get auto backed up to a directory outside the form directory.

Thanks everyone!
For now I'm going to stay with using a mySQL DB. I've used them before while using OpenCart for my site. Just never really had to deal with them directly. They say life is boring without learning something new everyday. Time to learn how to manage mySQL.