Thank You Thank You Thank You, that did the trick. I do need all the fields.
We use this form to do Fire Abaitment, we have 18 (A-R) boxes that corespond
with 18 Violations. we have to do it 3 times a year, so we have A-1, A-2,
A-3, B-1, ect. plus a few other thinga like "Fire Resistive Roof" "Water
Tank" we wnat to keep track of the old data to find trends. As far as I can
tell, we need all the fields. we sync this data onto PDAs to do the field
collection work & I dont want to have to re-sync the data to new DB each year
so I just copy, rename old & past the original back. All my sync's &
shortcuts still work.
No. You do NOT NEED to store your data in a non-normalized
spreadsheet. In fact it's much better, and much more flexible and
searchable, to store your data in a normalized structure!
If you have 18 violations currently... can you be ABSOLUTELY certain
that you might not have 20 next year, as the laws and technology
change? Do you really want to restructure your entire database just to
add another type of violation?
If you have a many to many relationship between dates, sites, and
violations, I'd suggest that you need a table structure such as:
Violations
ViolationID
ViolationDescription
Sites
SiteID
Address
<other info about the site, owner etc.>
INspections
SiteID ' where was the inspection done
VisitDate ' when
Violation ' what was found to be in violation
Comments
This will make it MUCH MUCH easier to determine trends, search for
patterns of violation, count the number of violations at a given site,
and so on and so on.
Do consider restructuring your tables!
John W. Vinson[MVP]