ۥ-x@ -Djjjjjjjx    B4j Crystal Reports Technical Document Subject: Error Message: Error Detected in Database DLL Date: August 31, 1993 Versions: VB 3.0 Situation: Error Message: Error Detected in Database DLL Solution: Check the following... SYMBOL 183 \f "Symbol" \s 10 \h Only one copy of distributed DLL's exist and are in the \WINDOWS\SYSTEM directory. SYMBOL 183 \f "Symbol" \s 10 \h Only one copy Crystal Reports exists on the development machine. SYMBOL 183 \f "Symbol" \s 10 \h Reports Created were created using Crystal Reports For Visual Basic 3.0 SYMBOL 183 \f "Symbol" \s 10 \h The report runs from the Visual Basic run (debug run). SYMBOL 183 \f "Symbol" \s 10 \h The report runs when compiled (MAKE.EXE) into an application directory on the development machine. SYMBOL 183 \f "Symbol" \s 10 \h Database file locations stored in the report are correct even when on the client's machine. This requires the use of the app.path global property to set the datafile properties in Crystal Reports. We Recommend using SAME AS REPORT if the datafiles are kept in the application's own directory as this will not require changing the datafiles' properties. SYMBOL 183 \f "Symbol" \s 10 \h If using graphics, include P3*.DLL in your distributed files. SYMBOL 183 \f "Symbol" \s 10 \h Make sure that you have all the correct files and that the system is not finding old files(dlls). SYMBOL 183 \f "Symbol" \s 10 \h Ensure that installable ISAMS section of your distributed VB.INI file are pointing at the correct location of the drivers when using external database files. You must have only one VB.INI in your Windows dirctory(Crystal will search the Windows directory for the ISAMs of VB.INI). You must have all of the installable ISAMs as shown below and all of the dlls must exist in the same directory as specified by each ISAM line. We recommend that the path definitions be the same for each ISAM and we also recommend that this path definition points to the Windows\System directory. VB.INI(only a portion of) [Installable ISAMs] Btrieve=C:\WINDOWS\SYSTEM\btrv110.dll FoxPro 2.0=C:\WINDOWS\SYSTEM\pdx110.dll FoxPro 2.5=C:\WINDOWS\SYSTEM\pdx110.dll dBASE III=C:\WINDOWS\SYSTEM\xbs110.dll dBASE IV=C:\WINDOWS\SYSTEM\xbs110.dll Paradox 3.X=C:\WINDOWS\SYSTEM\pdx110.dll (Xbase=C:\WINDOWS\SYSTEM\XBS110.dll) This line is optional [dBase ISAM] Deleted=On SYMBOL 183 \f "Symbol" \s 10 \h Normally, the FoxPro dll is specified as xbs110.dll, however,if you are using dBASE files this driver specification may conflict with the dBASE drivers. Therefore, change the FoxPro Line to point at pdx110.dll. SYMBOL 183 \f "Symbol" \s 10 \h Your VB.INI should be located in the Windows directory that is currently running. For example, if you are running Windows from a shared environment on a Network then Crystal will search for the VB.INI in that Shared Windows directory not on your local Workstation's Windows directory. SYMBOL 183 \f "Symbol" \s 10 \h If you are running your EXE from a network please ensure that your dlls are in a location that Windows can find them. Windows will search for the appropriate runtime files and dll in the following sequence: Current Working directory ---> Windows dir---> Windows\System dir--->DOS Path. If you have place your runtime files and dlls in your path and your application still does not seem to work, try placing the dlls in your Windows\System directory. SYMBOL 183 \f "Symbol" \s 10 \h If the datafiles are on a network, ensure that the mappings are the same on the client's machine. SYMBOL 183 \f "Symbol" \s 10 \h If you cannot get your application to run from the network then try loading CRW.EXE, CRW.NET and CRW.USR onto a network drive and then load the report from there. You will receive a more accurate error message from CRW than you would from your VB application itself. Once you can determined how to load a report from within Crystal Reports Design Mode then you probably won't have any problems with loading a report via an application. Remarks: This error message is generic message for a problem in running or loading the report. ERRDBDLL.DOC  GOjkDEde  )**245uv  ! @ A %&amN GRjD u^ ` }   : b acmhh-B X X   BTimes New Roman Symbol&Arial5Courier New 1Courier `/O/zj ` *X99999999999999$$h$$"h jإ6ڥ6ڥ<[Error in Database DLLTechnical Support Document Error DLLEProblem solving document for the error message Error in Database DLL.Allan D. McMordie Allan Moore