You do not want to store form data (data that someone fills into a form) in the same table that stores form schema (the data that describes your form). Conceptually, this is the same distinction as that between a class and an instance: the form schema is like a class, a filled-in form is like an instance of that form.
So, you have a table that lists forms and a table that lists fields on those forms. Great. To get the field schema for form @FormID:
Select *
From FormFields
Where FormID = @FormID
Presumably you then render the form in some way and allow the user to populate the fields. When saving, you should save this data somewhere else. You cold save this data in another set of tables:
Table: FormInstances
Field: ID int - form instance ID
Field: FormID int - link to table FormTable
Field: Name varchar(50) - a short descriptive name of this instance (e.g. Bobs expenses for 1/1/2010)
Field: Created datetime
Field: Edited datetime
etc.
Table: FormFieldData
Field: ID int
Field: FieldID int - link to table FormFields
Field: Value (this is the problem with an abstract system like this - what data type to use for the field values)
etc.
However, you're much better off using files to save your form schema and your form content while using a database to manage your forms. XML was created for this sort of thing (q.v. XForms).