You don't enter data in design view.
Create a table that replicates that structure. Then enter data in Datasheet view.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Hi June..yes you correct...but that was not i meant..
since the datatype is "Yes/No"... and im not quite sure which way to enter it..
do i have to enter each service like this
Fieldname
Do you have yourTea Spoon ---> Yes
Do you have your Tea cups --->yes
Do you have your Tea litres --->No
Do you have sugar for last 3 months-->NO
Table with 3 fields of name and type:
Service (text)
Tea (Yes/No)
Sugar (Yes/No)
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
hi
what about spoon,cups and liters...do i have to create it also?
After another look at your example, not really making sense. Is this a real database you need or a hypothetical scenario? What are spoon, cups, liters - units of measure? What exactly is this database supposed to be for?
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Examples reflecting the true situation are always better.
The field for each "Have you ..." question would be a Yes/No type. This is still not a truly normalized data structure. If you want to add more question, have to modify table, queries, forms, reports. Normalized would be:
tblAnswers
PatientID
ServiceID
QuestionID
Response
However, it is a balancing act between normalization and ease of data entry/edit. If you expect to never (or not for a very long time) have more than those two questions, then your structure might be adequate for your needs.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.