ۥ-1@ -    #(KKKKKKKKKMMMMMMk4MkkkCrystal Reports Technical Document Subject: MS Access Secured Databases Date: 11-Nov-93 Versions: VB Situation: Some users are having difficulty setting up MSAccess Secured Databases. Solution: First of all, make sure that the customers copy of the Access DLL's are up to date. These are the files that worked for our simulation of this problem. The files that came with the Visual Basic package may not be reliable for solving this problem. The following files are located in your Windows\System directory and must be updated: PDBJET.DLL PDCTJET.DLL PDIRJET.DLL What the user needs to do is download the file VBFIX.ZIP from our BBS. This file is in both area 5 & 6 on our BBS. The BBS number is (604) 681-9516. VBFIX has these three DLL's(as shown above) that will replace the ones in the user's Windows\System directory. Find the outdated files in the customer's Windows\System directory and copy them to floppy disk so that he may have them for future reference. The next step is to add the following line to the user's VB.INI file. If the user has Crystal Reports, Visual Basic, or MSAccess loaded, he must quit all those applications and restart the application, to recognize the changes. This change in VB.INI must also be reflected in the application distribution disk, and all machines that use an application accessing a secured database. (IN VB.INI) [Options] SystemDB=(Path to Access directory) \SYSTEM.MDA Now when you assign a password to the Admin account, you can still load the report in Crystal, but you are prompted to enter the Admin password before you can print the report. If the Admin account is removed, then the user is prompted to type in his name and password, hence keeping the integrity of the Secured Database. SECURED.DOC (MRE) GR bpB  EGRsuBD!!!!W!! !T!#!$2F +"0MO00(Times New Roman Symbol&Arial%"hZۅߺE[MSecured Database (MSAccess)Monte EricksonAllan D. McMordie