• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 11. Modifying Data with Action Q... > In the Real World—Alternatives to Ac...

In the Real World—Alternatives to Action Queries

Microsoft calls any Access query that alters table data an action query; the more common name is update query, as in updating the database. With Access, however, there's a good reason to distinguish graphical action queries from the update queries used in online transaction processing (OLTP). Access's graphical action queries are intended primarily for bulk operations—adding, altering, or deleting large numbers of records in a single operation. OLTP usually deals with a single record or a few related records per operation. Creating a new Access action query each time you must update a single record clearly is an inefficient process, even if you add a parameter to designate the record you want to update or delete.

Note

The sections that follow deal with advanced Access topics, which are covered in detail by chapters later in this book. In the real world, production databases reside on a file or application server and multiple users connect their client PC's front-end applications to networked shared-file (Jet) or client/server (MSDE or SQL Server) databases. Chapter 24, "Securing Multiuser Network Applications," and Chapter 25, "Creating Access Data Projects," deal with shared-file and client/server-type databases, respectively. The purpose of this In the Real World episode is to demonstrate the many options that Access offers for executing action queries and their equivalents.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint