Autofill microsoft access 2007

Access UI weirdness -- text selection permanently on. Access Rich Text Deficiencies? Access Autofill Numbering. Mobile Development.

Software Development. Remote Development and Debugging Tools. Adding a new footer. Ms access. Undesired Name? Follow us! Get the Latest Bytes Updates. By using this site, you agree to our Privacy Policy and Terms of Use. Oct 14 '10 reply Message. Cancel Changes. General lancet: a comprehensive, efficient, and reusable util function library of go reply views Thread by lanliddd last post: by.

General Adding a new footer reply views Thread by Kaata last post: by. One of the detail will be a CategoryID selected from a table of categories. On your table where you select the medicine, you would do so in a foreign key field also named MedicineID.

If you want to display the category on your form see my blog on Displaying Data from Related Tables. One of the principles of relational databases is that data exists in one place only. So repeating the medicine name in your records and repeating the category is not correct design. I would suggest familiarizing yourself with the concepts of normalization, the key principles for relational database design. You may need to revise your table design. Was this reply helpful?

Yes No. Sorry this didn't help. Thanks for your feedback. I'm not intending to repeat either of these things. I only want the medicine name and category to appear once each. I therefore don't see how I am violating the principle of normalization to which you refer.

Here's a screenshot that may add some clarity:. You can see the medicine names in the highlighted field. I want the medicine categories to appear in the first empty field on the right. How would doing this be repeating the presentation of data? Also, even if it would mean that, why does that matter?

I didn't say you are repeating the info per record but you are repeating the info in the table. Look at the bottom of the screenshot, In records 60 and 62 the name Paracetamol is in 2 different records. So you are repeating the name. I also see that you only have ONE table. You should have at least FOUR tables:. You do NOT need the Category in the last table since you can pull the category from tblMedications in a query or on a form. Threats include any threat of suicide, violence, or harm to another.

Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect. Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software.

Unsolicited bulk mail or bulk advertising. Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation. Details required : characters remaining Cancel Submit 4 people found this reply helpful. I'm not going to comment on whether it is more or less repetitive to have four tables rather than one.

As it stands, the table I have looks most like the final table in your list of four: and the only information I wish to add is the medicine categories. I see little point in going back to the start and making three more tables out of these 7, records when all I want is one more field.

So, I repeat my original question: is there a way to quickly categorise these medicines in a new field? I do not think you will find any experienced respondent here who is prepared to assist you in continuing a fundamentally flawed model in which the table is open to the risk of update anomalies, resulting in an unreliable database.

The process of normalization is a formal one which eliminates redundancy by decomposition of a non-normalized table into two or more related tables. The first three normal forms are formally defined as follows: 1NF: First Normal Form: A relvar is in 1NF if and only if, in every legal value of that relvar, every tuple contains exactly one value for each attribute.

Loosely speaking, in the language of the relational model, a relvar relation variable equates to a table, a tuple to a row record and an attribute to a column field. There are higher normal forms, whose definitions you can easily find online, but in most cases a table normalized to 3NF will be normalized to the higher normal forms also.

This is not to say that these higher forms can be ignored, however. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Access for Developers. Sign in to vote. I am using MS Access Thanks for help. Friday, September 7, PM. Do you want to add it?