Employee Phone Directory

[startingover04]

I am new to Microsoft Access and still learning. I am trying to build an Employee Phone Directory and I have the following table built:

EmployeeList
EmployeeID LastName FirstName OfficeExtension JobDescription

I want to build a query that pulls the staff can use a form to pull the LastName, FirstName, and OfficeExtension, by requesting the staff members LastName and FirstName in Message Box that comes up and all they get is the form with the information that they requested. I do not want them to see my database, just to see the form with a command button on it to bring up the message box to put their information in it and then their results.

Since I am new to Access, I am having trouble getting this to work. I have the table and I had the form built, but I am having trouble with the query and the marco.

I would appreciate anyone's help on this. Thanks,

 

[fneily]

I would create a query that concatenates the first and last name of each record. Then I would base a form on this query to show the appropriate fields. I then would have a combobox based on the concatenated field from the query. Then the user can just select a name from the combobox which then would run code to display the info.

But if this is all you want to do, Access is overkill. Just create an Excel list (follow the rules for building a list) and then use the Autofilter feature. Alot easier for you.

 

[startingover04]

Thank you, but we have at this time 330 employees at 8 locations and our CEO wants to use this database for others things too. We are going to use this database for their email addresses, departments, office locations, etc.

 

[fneily]

Small and simple data. If you're new to Access, this would probably be nice to start with. Also, this would be a good introduction to Normalization. You must normalize your tables first or you're not using Access correctly. And then set up the correct relationships. Do both of those before inputting any data.
With what's presented, my gut feeling is that your CEO doesn't know Access or advance Excel functions. Oh well.

 

[lespaul]

ok, if you are also going to be adding some of these other features in the future, you should really think about how to implement them without compromising existing information. For instance, does the phone number belong to the person or the office they occupy? It belongs to the person if when they move to a new office they keep the number. If however, the person's number changes when they move it belongs to the office. If it belongs to the office, then you need to remove that from the Employee table and create an office table because 'phone number' is an attribute of the office entity. A person's name is an attribute of the person.

You need to identify your entities and their attributes, that will determine your tables and your fields. Read the fundamentals document below for more information on how to accomplish this.

Leslie

Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual

Essential reading for anyone working with databases:
The Fundamentals of Relational Database Design
Understanding SQL Joi