Chapter 24. MOVING WORKGROUP APPLICATIONS TO CLIENT/SERVER
IN THIS CHAPTER
For many different reasons, a day might come when using Access as a front-end development tool and as back-end storage for data is no longer optimal for your applications. At this point, you should consider a client/server solution. Access provides developers the flexibility of storing data in various storage formats, including dBASE, Paradox, FoxPro, Excel, Lotus 1-2-3, text files, and ODBC databases.
This chapter focuses on migrating the data in your Access applications from Jet to SQL Server to create client/server solutions. After reading this chapter, you should have a better understanding of how to plan for client/server migrations and how to carry them out. You also learn a few specifics about using the upsizing tools with SQL Server versions 6.5 and 7.0.
Note
When SQL Server is mentioned in this chapter without a product version number, it means either of the two versions that are used with Access 2000 client/server applications: SQL Server 6.5 and 7.0. Where version-specific behavior is discussed, the version number is included in the text.