How do I fix my too many fields defined Problem?

[mpyers]

I have a database I'm building to replace a paper form. This is a quality inspection form. We have 35 Quality checks we do every few hours for each line. The form they have now is 2 pages. The front page is information about the job. The back page is the inspections.

I want to create the database form in such a way that it will look identical to the hourly employees using it.

I created four tables, three for the information on the front page, and one for the inspections.

When I created the form, I got halfway through the front page, and I am now running into "too many fields defined". There is a section that has an option for every half hour of production (Running, set-up, maintenance, etc.) With 8 options to choose. For this I used a Boolean value for each option on each time slot. Meaning 192 fields. This has its own table, but when I entered it into the form, I started getting the error message. I tried to delete the fields, planning on putting them on their own form, but I still get the message after I deleted them.

This is my first database, so be easy on me.
I get the idea that you want to have many related tables, but I wouldn't have thought that there would be a limit to the number of fields on the form, talking to each table.

What should I do instead of using 196 Boolean values. I still want that many check boxes on the form, because that is currently how it is done on the paper copy.

It is important that the form look and print identical to the original.

[TheSmileyCoder]

I remember reading somewhere that Access has a counter for controls on a form. If you add a control, access probably internally stores it as Control616.
Those numbers are not re-usable, so there is in effect a limited amount of times you can add/remove a control from a form, and I believe that is why you can no longer add controls to your form.

Could you provide an image of what the paper form currently looks like? That will probably make it easier for us to suggest alternative approaches.

[mpyers]

[mpyers]

As you can see. Not every field will always be relevant for a particular product.

The SO # is the main identifier.
The item # is the secondary identifier.

I ran out of fields at the "Development" Section of the bottom grid.

[TheSmileyCoder]

I see. What you could do is to move some of the information into a subform. That said, it seems from your pictures that stuff like box is really related to many records. The 2 boxes in your example have nothing to do with each other correct? In that case it should be in seperate rows.
Also the lost time part seems to lend itself to a subform, with new records appearing as needed, instead of showing 12 blanc records. Does that make sense?