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

WORKING WITH PROJECTS

You've probably already created Jet-centric Access applications consisting of two primary components: a front-end application database with queries, forms, reports, and modules, and a related back-end database with the data tables. In an Access Project, the front-end/back-end concept is employed but in a different model. In the front end (an Access .adp file) are forms, reports, and modules with VBA code. The back end (a SQL Server database) consists of the queries (called views), the data tables, and more application code in modules called stored procedures. Because the views and stored procedure code are in the back end, the processing of data retrieval and other data manipulation is optimized for maximum performance and minimum network traffic; thus, an Access Project fits the definition of a client/server application.

Note

The Access Project model fits the two-tier client/server model, defined as having front-end and back-end components. A different client/server model, known as three-tier, can also be used with Access but requires additional development tools (Visual Basic or Visual C++) to create the COM components that manage data in the middle tier. It's easier to use a Jet-based application in a three-tier model than it is to use a Project, because the Jet-based application can provide temporary local tables and queries that can be used for bulk local data manipulation and with forms and reports. An Access Project doesn't provide any local storage for table data.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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