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

Chapter 19. Linking Access Front-Ends to... > Choosing a Client/Server Migration S...

Choosing a Client/Server Migration Strategy

Prior to the introduction of Access 2000, linking was the only method of migrating Access applications from Jet tables to client/server databases. The primary advantage of linking client/server tables is that the Jet 4.0 database engine running on the client processes your Jet SQL queries. Thus, crosstab queries continue to execute as expected, and you can use MSGraph objects in your forms and reports. Linked client/server tables let you take advantage of Jet passthrough queries to send Transact-SQL (T-SQL) statements directly to SQL Server, PL/SQL to Oracle, or any other SQL dialect to your RDBMS. The downside of linking is that you lose the efficiency of server-side query processing, which is one of the most important features of client/server RDBMSs. The sections that follow describe Access 2003 options for moving to SQL Server databases.

Note

You create passthrough queries by opening a new query in Design view, closing the Show Table dialog, and choosing Query, SQL-Specific, Pass-Through to open an empty Query1: SQL Pass-Through Query window. In the window, type the query’s SQL statement in the SQL dialect of the server, and then close the window and save the query. When you execute the query, Jet sends the SQL statement to the linked database for execution. If the SQL statement returns rows, the query result set opens in Datasheet view.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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