Microsoft Office Access 2013 Complete In Practice 1st Edition By Annette Easton and Randy Nordell -Test Bank

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

True    False

TRUE

When you create a database built from one of these templates, you must link it to a SharePoint server running Access Services.

TRUE

Most templates open with the Navigation pane closed.

FALSE

Design view is not an available option for objects in web databases.

TRUE

For web databases, Access provides enhanced Datasheet view features as well as the Layout view functionality.

TRUE

After completing the Lookup Wizard, Access automatically creates a relationship between the two tables.

FALSE

The Row Source Type and Row Source properties are set automatically by the Lookup Wizard.

TRUE

SQL is the underlying language in a relational database system.

FALSE

A many-to-many relationship exists when many rows of data in one table can be associated with many rows of data in a second table.

TRUE

Relational databases, like Access, do not directly support many-to-many relationships.

TRUE

The join type property determines how to match the data in the two related tables.

TRUE

When a relationship is created, Access assigns it an inner join type.

TRUE

Changing a relationship’s join type only affects the way queries, and any object built from a query, work.

TRUE

A macro is a database object that allows you to write and attach code to different objects and controls in your database.

FALSE

Macros in Access are very different than the macros you may have created in Excel or Word.

TRUE

Events are occurring all of the time when you use a database.

TRUE

User interface macros are attached to objects and controls, such as forms, reports, and command buttons, that are part of the user interface.

FALSE

Comments do not affect the logic or functionality of macros.

TRUE

A stand-alone macro is a separate Access object that appears in the Navigation pane.

TRUE

An embedded macro is attached to one specific object or control on an object.

TRUE

You can create a stand-alone macro that executes automatically when the database is first opened.

TRUE

The property sheet of an object or control displays all the possible events on the Event tab.

TRUE

Create a stand-alone macro when you want to call a macro from several different objects or controls.

TRUE

A macro that runs when a database is first opened is an AutoExec macro.

TRUE

Before creating an embedded macro, you must first open the property sheet of the object or control.

TRUE

An embedded macro is automatically created when you use the Command Button Wizard to attach functionality to a button.

TRUE

Edit a stand-alone macro by right-clicking the macro name from the Navigation pane and selecting design view.

FALSE

Edit an embedded macro by opening the property sheet of the object or control and clicking the Build button in the property box of the event.

TRUE

A submacro is a named, executable set of actions that perform a specific task.

FALSE

Using a parameter in a named data macro allows you to pass data into a macro.

TRUE

The Macro Builder contains the Single Step tool, which can execute the macro one action, or step, at a time.

The Desktop issue tracking template is used to track information about reported issues that need to be resolved.

The Desktop asset tracking templates is used to track assets within an organization, such as computers or office equipment.

The Desktop project management template is used to track information about different projects and their related tasks.

The Desktop contacts template is used to track information about people, such as team members, customers, etc.

Design view is not an available option for objects in web databases.

After completing the Lookup Wizard, Access automatically creates a relationship between the two tables.

The List Width Lookup field property determines the width of the drop-down list.

The Allow Value List Edits Lookup field property determines whether a user can edit the list of items.

The Limit to List Lookup field property determines whether a user can enter a value into the field.

The List Rows field property sets the number of choices that display in the list.

Structured Query Language is the underlying language in a relational database system.

All of the statements are true.

Both of the statements in A and B are true.

When implementing a many-to-many relationship, if you perform each of the tasks listed, your database will most likely function correctly.

Press and hold the Shift key to select multiple foreign keys.

A left outer join returns all the records from the table on the left side of the join and only the records that have a matching value from the table on the right side of the join.

An inner join returns only records that have matching values in both tables.

The join type property determines how to match the data in two related tables.

A right outer join returns all the records from the table on the right side of the join and only the records that have a matching value from the table on the left side of the join.

When a relationship is created, Access assigns it an inner join type.

A macro is a database object that allows you to write and attach code to different objects and controls in your database.

All of the statements are true.

When creating a macro, you need to decide on the event that will cause the macro to execute; plan out the logic behind the steps, or tasks, the macro will perform; determine the type of macro needed; and choose the best way to build the macro.

User interface macros are attached to objects and controls, such as forms, reports, and command buttons, that are part of the user interface.

Events occur when an action happens to an object or control.

Data macros are attached to tables.

A program flow statement provides organizational structure to a macro.

The Comment program flow statement is the most common type of program flow statement.

An Action is an individual command inside of a macro.

You write and edit the content of all macros using the Macro Builder.

An If block lets you integrate conditional logic into the execution of a macro.

An argument is a piece of information needed to complete an action.

A group is a named block of actions.

A submacro is a named, executable set of actions that perform a specific task.

Ctrl+V lets you paste an action.

Ctrl+C lets you copy an action.

The Data Entry Operations category of user interface macros relates to changing the data.

The Database Objects category of user interface macros relates to changing controls and objects in the database.

The Filter/Query/Search category of user interface macros relates to filtering, querying, and searching records.

The Data Import/Export category of user interface macros relates to importing, exporting, sending, and collecting data.

The User Interface Commands category of user interface macros relates to controlling what is shown on the screen.

The System Commands category of user interface macros relates to changing the database system.

The On Got Focus event executes when an object/control receives focus.

The On Enter event is only used with text box controls.

The On Click event executes after the object/control is clicked.

The On Exit event executes immediately before a control, on a form or report, loses the focus to another control on the same form or report.

The On Key Up event executes when the user releases a key that he or she was pressing.

The On Mouse Up event executes when a mouse button is released after having been pressed.

The On Activate event executes after a form or report is already opened and the object gains the focus.

The On Open event executes when a form or report is opened.

The AutoExec macro runs when a database is first opened.

All of the methods listed will run a stand-alone macro.

To bypass the execution of the AutoExec macro, a user can hold the Shift key down when opening the database.

The After Update data macro event executes after an existing record is changed.

The EditRecord data block macro action changes the values in the existing record.

The RaiseError data macro action notifies the application that an error has occurred.

The CancelRecordChange data macro action exits an EditRecord or CreateRecord data block and does not save the current record.

Using a parameter in a named data macro allows you to pass data into the macro.

In data macros, the Application Log is available to help you debug a macro.

The MacroBuilder contains the Single Step tool, which can execute the macro one action, or step, at a time.

You can choose from several templates that are included with Access. Additionally, there are other templates available on Office.com. Some of the Access templates are designed to work on the web. When you create a database built from one of these templates, you must link it to a SharePoint server running Access Services. The non-web-based databases are designated as desktop databases in Access. The following database templates are included with Access: Desktop asset tracking, Desktop contacts, Desktop issue tracking, Desktop project management, and Desktop task management.

Relational databases, like Access, do not directly support many-to-many relationships. You must create a junction or intersection table to match up the records. A junction table changes the many-to-many relationship into two one-to-many relationships. The guidelines for creating a junction table are fairly straightforward; however the application of these guidelines takes a little bit of practice.

After designing the tables in a many-to-many relationship, you must create the tables and set the field properties in your Access database. Keep in mind the following tips to ensure your database will function correctly:

• Build the tables on the “one” side of the relationship first.
• Define the primary key for each of the “one” side tables.
• Build the junction table. The foreign key fields should be the same data type and size as the matching field in the “one” side table. If the primary key in a “one” side table is an AutoNumber data type, then the foreign key field should use a Number data type. Both fields should have the same number subtype, as indicated in the Field Size property.
• Define the primary key for the junction table. Remember that this table represents the “many” side of each relationship.

Most macros execute because an event occurred in the database. An event is something that occurs when an action happens to an object or control. Events are occurring all of the time when you use a database. For example, when a report or form opens, the On Open event occurs. Likewise, when a user hovers the mouse over a button on a form, the On Mouse Move event occurs. Or when a user presses a button on a form, the On Click event occurs. Even table objects have events. For example, when a user changes a value in a field, the Before Change event occurs. The Event tab of the property sheet contains all the events that a form or report object, or a control placed on one of those objects, can respond to.

You write and edit the content of all macros using the Macro Builder. The Macro Builder contains the macro window, the area where you enter and edit the action steps of the macro. The right side of the Macro Builder displays the Action Catalog. The Action Catalog contains a Search box, Program Flow folder, and Actions folder. Use the Search box to locate an action. The Program Flow folder contains four macro statements. A program flow statement provides organizational structure to the macro. The Actions folder contains the different actions, grouped by category, that are available to add into a macro. An Action is an individual command inside of a macro. You can expand any of the categories in the macro window to view the specific actions.

Many of the macros you build will be attached to different parts of your database’s user interface. There are two types of user interface macros, stand-alone macros and embedded macros. A stand-alone macro is a separate Access object that appears in the Navigation pane. You can use a stand-alone macro independently of any other object. Additionally you can assign it to events in many different objects, allowing you to reuse the same macro. For example, you may want to create a message box to display the same message in many different forms or reports. You can create a stand-alone macro to display the message box and then attach that macro to each form or report. An embedded macro is attached to one specific object or control on an object. Embedded macros do not display in the Navigation pane. They are automatically executed by the object or control. Embedded macros are useful to automate tasks that are unique to a specific form or report in the database.

In contrast to user interface macros, data macros allow you to automate tasks related to the database tables. You can use data macros to ensure that the data in tables is accurate. Additionally, you can use them to automate tasks related to adding, deleting, or changing data. Because these macros are attached to a table, they execute any time a table’s data is updated.

A named data macro is associated with a specific table, but it is not attached to any particular event. Instead, a named data macro is run by another event-driven macro or by a stand-alone macro. Named data macros have the following characteristics:

• They can use all of the data block actions and all of the event actions.
• They can use an additional action, SetReturnVar. SetReturnVar sets the value of a variable to be returned, or passed back, to the object that called the named data macro.
• They can use parameters, if needed. Parameters pass a value or an object reference into a macro. The name you assign to the parameter (in the name box) is the name you use to refer to the parameter inside of your macro.
• Named data macros are executed by using the RunDataMacro action to call the named data macro. Call a named data macro from an event-driven data macro or from a user interface macro.

Occasionally you may need to create a submacro, which is a named, executable set of actions that perform a specific task. Once you create a submacro, you can call that submacro when you need to execute that task. Creating submacros can be a useful organizational approach; you end up with fewer separate, smaller macros when you use submacros. You can only create a submacro in a stand-alone macro, and the submacro must appear at the end of the stand-alone macro. The only thing that can follow a submacro is another submacro.

After you create a macro it is important to test it to ensure that it performs as planned. With some macros you may not be sure that they are performing as expected unless you develop a plan to test the macro. This may involve creating test data and test scenarios in your database. As you are developing your databases, you may need to create or modify the sample data in the table(s) in order to test all possible conditions of a macro. With some macros you may discover that a logic error results from selecting the wrong event to trigger the macro. For example, imagine that you want to create a stand-alone macro that executes whenever a form is closed. You have a Close Form button on every form, so it is logical to attach the macro to the On Click event of the button. However, you need to think of different scenarios and ways the database may be used. For example, is it possible that someone might close the form by clicking the X in the corner? In that situation, your macro would not be executed. In this case, the correct event to attach the macro to is the On Close event for the form. In addition to creating test data, there are other tools available to help you debug macros. With user interface macros, you can debug a macro by adding error handling into a macro or by using the single step utility. With data macros, you can use Error Handling and the application log table.