Excellent! I can have one form where the top section contains the main record and another section (the CFGRID) has all the comments and/or deficiencies associated with that record. Just what I want! Sorta!
I got it to work, but for several of the columns I need a <select> that provides the user with pre-defined data. So I tried this:
<cfgridcolumn name="gridQDCategory" header="Category" headeralign="LEFT" dataalign="LEFT" bold="No" italic="No" display="Yes" headerbold="Yes" headeritalic="No"> <cfquery name="qCat" datasource="dashboard" dbtype="ODBC"> SELECT * FROM ValtblCategory ORDER BY CategoryID </cfquery> <select name="Cat" id="idCat"> <cfoutput> <option value="" selected>-- Select Category --</option> <cfloop query="qCat"> <option value="#CategoryID#">#CategoryDescrip# </option> </cfloop> </cfoutput> </select>
I believe the computer laughed at me and my ignorance. But it did give me exactly what I asked for: a fancy cfgrid of the columns I designated and a fully functional <select>, just outside the grid. Not what I wanted, but Garbage In Garbage Out. So my question is "How do I achieve the concept of a subform (multiple records) related to a single record and still allow <select> options for some of the fill in the blanks?"
Because of the variability in comments associated with a record I don't believe hard coding a bunch of rows and controlling the visibility as a row is completed is the answer.