Share this Page URL
Help

Chapter 19. Linking Jet Applications to ... > Using the Upsizing Wizard with Linke... - Pg. 795

Linking Jet Applications to Client/Server Tables Note 795 ChangeServer creates a test connection to the destination server to prevent deleting the first existing link. The properties of linked TableDef objects are read-only, so the existing link must be deleted before adding the new TableDef. Using the Upsizing Wizard with Linked Jet Tables The most common configuration for production Jet applications separates data objects into a front- end (client) .mdb file to hold application objects and a back-end .mdb file that contains only tables. Multiple users access the back-end file from a shared Windows NT/2000+ folder. You also can share the back-end file on a peer-to-peer server running Windows 98/Me, or Windows /NT Workstation/ 2000+ Professional. All users must have read/write permissions for the share because they must be able to write to the lock ( FileName. ldb) file. Under WindowsNT/2000+, you can apply user- or group-specific write permissions to the back-end data .mdb file if the server uses the NTFS file system. To review .ldb file basics, see "Jet Record-Locking Information Files". As mentioned earlier in the chapter, upsizing the back-end .mdb file and attempting to use the existing links in the front-end .mdb field doesn't work. Thus, you use the process described in the earlier "Running the Upsizing Wizard" section to upsize the front-end file and abandon the back- end .mdb. Splitting a single-user application prior to upsizing, however, lets you compare the per- formance of a Jet multiuser application with its client/server counterpart. Note