Over 250 Fields

[Jaz]

I have a medical assessment form that I must mimic and it contains 309
fields. I know that sounds really extreme, however each question is unique
and consists of true/false questions. How on earth do I go about creating
the table structure and form for data entry when we can only have 255 fields
max? Any ideas?

 

[Rick Brandt]

I have a medical assessment form that I must mimic and it contains 309
fields. I know that sounds really extreme, however each question is
unique and consists of true/false questions. How on earth do I go
about creating the table structure and form for data entry when we
can only have 255 fields max? Any ideas?

Hint; each question is a record, not a field.

 

[Jaz]

I am relatively a newbie and I do not understand what you are saying? How
can I create a form for data entry if it goes into a record instead of field?

 

[Rick Brandt]

I am relatively a newbie and I do not understand what you are saying?
How can I create a form for data entry if it goes into a record
instead of field?

Think of a classic order form. Main form for the order header, subform with
one or as many child records as you need for the items on the order. Same
principle except instead of a subform record being an ordered item it is a
question.

 

[John W. Vinson]

I have a medical assessment form that I must mimic and it contains 309
fields. I know that sounds really extreme, however each question is unique
and consists of true/false questions. How on earth do I go about creating
the table structure and form for data entry when we can only have 255 fields
max? Any ideas?

For a normalized design for questionnaires which handles any number of
questions see


http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='At Your Survey 2000'

 

[Jeff Boyce]

Rick & John are pointing you toward using Access as a relational database.
You've described trying to make Access work like a big spreadsheet (it isn't
one).

Just because you want to be able to "mimics" a form you already have doesn't
mean your TABLE has to. Check into queries.

There are (at least) three major learning curves in learning to use Access:
1) relational database design and "normalization" (repeat after me,
"Access is NOT a spreadsheet")
2) using the features/functions in Access
3) graphical user interface design (you did want folks to be able to use
this, right? without learning Access, right?!)

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP