Proper MS Access Customer Contacts Database Design Tips
By: chris howe
Submitted: 2010-02-12 23:48:20 | Word Count: 722
Coming up with an MS Access database with no help of knowledgeable Microsoft Access consulting companies is able to be done, allowing that you understand the basics of proper database design methodologies. After you have determined the purpose of your MS Access database, you may want to seek out and organize required information that can be stored in your Access database.
To search out and organize the data required, start with your existing information. As an example, you would possibly record consumer data on paper forms in a very ancient file cabinet or an Excel spreadsheet. Gather those documents and list each type of data shown (as an example, each box that you fill in on a form). Break the fields down to their basic form, such as initial name and last name, rather than merely "name." If you don't have any existing forms, pretend you've got to design a form to record the client information. What data would you place on the new form? What knowledge components would you prefer to store or perhaps run reports on in the future? Maybe you wish to know how several fishing lodge guests that stayed with you in the past 2 years live in Alaska? Determine and list each of those items. Another example, suppose you currently keep the fishing lodge guests list in a paper notebook. By closely examining these entries, you would possibly discover every entry contains a customers name, address, town, state, postal code and telephone number. Each of these things represents a possible column in a very detailed table.
[ advertisement ]
As you prepare this list, don’t worry about getting it perfect or complete on your first attempt. Instead, list each item that comes readily to mind and remember that an MS Access database is an easily modifiable tool. If somebody else in your business will be using the database, ask for his or her input. You'll be able to perpetually modify the table so long as you don't have dependent programs relying on the information fields. This is often not rocket science and you typically will not require to employ the services of an knowledgeable affordable Access consulting companies to increase the table.
Next, think about the types of reports, bulk emails, or brochure mailings you might wish to supply from the new database. As an example, you may need sales reports to indicate fishing lodge guests by country, or a list outline report that displays room or fishing charter boat inventory levels. You might also need to generate form letters to send to purchasers that details special sales. Design these probable reports in your mind, and imagine what it'd appear as if it were sitting in front of you. What info would you place on the report? List each item. Do the identical for the shape letter and for any alternative report you anticipate needing to conduct your daily operations.
Giving careful thought to reports, bulk email and brochure or flyer mailings helps establish knowledge things you will need in your business database. For instance, suppose you offer Alaska hunting lodge clients the opportunity to opt in for newsletter, and you would like to print a listing of those that have opted in. To store that information, you add a "SendEmail" column to the hunting lodge's client table. For each hunting lodge guest, you can either set the field to Yes or No, True or False, or 1 or 0.
Wanting to send Email newsletters to Alaska hunting lodge guests suggests another data purpose to store within the table. Once knowing that hunting lodge guests need to receive Email newsletters, you'll conjointly would like to grasp the Email address to that to send them. Therefore you need to record an Email address for every hunting lodge guest if available.
To design your table, ponder on these items carefully. Even knowledgeable MS Access database designers want to return and add information elements. This may occur moments once saving the table, or years when the need arises to increase the functionality of the database.
