when to use tables

[atomic.argonaut]

say you've got a form thats responsible for collecting data on an individual pertaining to first name, last name, middle initial, address, state, zip, etc.

is it good web etiquette to use a table for organizing the input fields and then returning the entered data in the same table, or should you use a table to organize the returned data only?

and if the best way is to only use table markup for the returned data only, whats the most effective method for organizing the input fields? unordered lists? a separate div for each field? thoughts? thanks!

[JefferyJamison]

Hi ! As per my Opinion the best way is to use table for organizing the input fields and then returning the entered data in the same table with different font style. It is the helping when you have some query or problem then you easily manage it.

[atomic.argonaut]

hey there, thanks for the reply. as well as that thanks for prefacing the message with 'as per my opinion.' its refreshing when people dont view themselves as the end all authority on a given topic.

anyway.

while i agree that structuring the form using a table, and returning the data to that very same table is, from a workflow standpoint, the most convenient thing to do, my question is is it semantic?

most everything ive read in relation to table usage stresses that it only be used for the tabular arrangement of data.

given that forms arent data, but a method of collecting it, im wondering if using tables for their arrangement is considered proper.

thanks!

[SB65]

You've sort answered your own question about when tables should be used, I think. The general consensus is that they should not be used for layout.

Here's a couple of useful links on laying forms out without tables:

http://alistapart.com/articles/prettyaccessibleforms
http://www.noupe.com/php/beautiful-forms.html

The first of these is quite old, but still useful I think.