Public Schedule Face-to-Face & Online Instructor-Led Training - View dates & book

access basic

Forum home » Delegate support and help forum » Microsoft Access Training and help » Access (2010) - basic question

Access (2010) - basic question

ResolvedVersion 2010

Simon has attended:
Dreamweaver 8 Introduction course
Access Intermediate course

Access (2010) - basic question

Hi,

I'm really struggling with getting to grips with a very basic aspect of Access and would appreciate your advice.

I'm designing a database which will mostly be concerned with entering, presenting and searching text fields of various kinds. After my training session on Monday I got to work, creating lookups to enable Access to pick up text from other tables in combination with free text fields so that I could construct larger tables from smaller pieces of information - eg name, department, work role etc. But having done this and when I look at the relationships view I see that creating the lookups has already created a web of relationships between the tables. And I've no idea how to develop the database further from this point. I've read that look-ups are not good design practice, and now I'm confused about the practice of table relationships - how to pick information from one table for use in another - eg. a person's name being added to another table about a project. I understand the theory of relationships, primary keys and foreign keys etc. but not how to design something that will enable a user to actually get information from one table to another and how much of this should be done at table level, query level and form/report level? If I can answer this puzzle I think I'm on my way as the course was otherwise clear. I really need to be getting on with this and feeling very frustrated.

Many thanks
Simon

RE: Access (2010) - basic question

Hi Simon,

Thank you for the forum question.

The only thing we have in the tables are the records. Each table should follow the normalization rules explained on the intermediate course. How we should relate the tables depends on the database and structure. Relationships can be created from the relationship window or using lookup fields.



If you follow the normalization rules you will know which information I should have in each table.

Only have the same information in 2 tables if it is needed for the relationship.

If you need to merge the information from many fields from many tables you must do this in a query not in a table. You can then create forms or/and reports based on the query.

I hope this can be a help. You can also get inspiration from Microsoft's sample database "Northwind" which can be downloaded free from Microsoft's website.

Kind regards

Jens Bonde
Microsoft Office Specialist Trainer

Tel: 0207 987 3777
Best STL - https://www.stl-training.co.uk
98%+ recommend us

London's leader with UK wide delivery in Microsoft Office training and management training to global brands, FTSE 100, SME's and the public sector

Sat 12 Jul 2014: Automatically marked as resolved.

Access tip:

Relationship maps

It is important to create proper relationships between tables. You can use Access to help check your designs and evaluate them by printing them in graphical format to help with design purposes


Click on the Tools menu, click Relationships.
On the File menu, click Print Relationships. View or print as required

View all Access hints and tips

Connect with us:

0207 987 3777

Call for assistance

Request Callback

We will call you back

Server loaded in 0.16 secs.