still messy behind the scenes but will tidy up as I learn more thankyou,,
You can't just say you'll fix the crumbling foundation once the upstairs bathroom is painted the right color. You need to focus on your table structure now and put aside your input forms. Read up on normaliztion:
en.wikipedia.org
That's the process of properly setting up your tables/fields. The big issue you have is using values as field names. You do this a lot, but let's focus on GCS_Calc. [EYES], [VOICE] and [MOTOR] should not be field names, instead they should be values in a field. The proper way to structure that table is like so:
gc_ID, autonumber, primary key (currently [ID] field)
gc_Type, text, this will hold whether the records if for VOICE, EYES or MOTOR (those are the values it will hold)
gc_Description, text, this will hold the corresponding values in the EYES/VOICE/MOTOR fields
[GCS_FK] goes away because it serves no purpose. That's it, those 3 fields above will hold all the data you need for this table. Instead of 6 records with 3 null values you will have 15 records to accomodate all the EYES/VOICE/MOTOR fields with data in them.
Again, that's just one example, you've done the same thing with PT_GCS, PS, Secondary Survey and Observations--using values that should be in the table as names of fields. Put aside whatever this issue is about and work on your tables.