ۥ-x@ -y     #Beeeeiiiiikkkkkk4Crystal Reports Technical Document Subject: VB and CRW 2.0 coexisting on the same system Date: August 23, 1993 Versions: 2.0(Std), 2.0(Pro), VB Situation: Crystal Reports 2.0 and Crystal Reports for Visual Basic can be used in the same system with a few modifications. When installing Crystal Reports 2.0 into the CRW (Crystal Report Writer) directory, all of the DLL files are placed within this directory; however, when Crystal Reports for Visual Basic is installed, all of the DLL files are placed within the WINDOWS SYSTEM DIRECTORY. Therefore, each version of Crystal Reports can act independently without conflict. If, however, you wish to use NTX indexes from Crystal Reports for Visual Basic you must copy the PDBXBSE.DLL from the CRW directory into the WINDOWS SYSTEM directory. It should be noted that Crystal Reports 2.0 is a lower version than Crystal Reports for Visual Basic and, hence, reports created in Visual Basic cannot be accessed via the Crystal Reports 2.0 dynamic link library. When an external application requires the use of a Crystal Reports Print Engine call, it will always use the CRPE.DLL located in the WINDOWS SYSTEM directory. This CRPE.DLL is installed by Visual Basic and therefore corresponds to the Report Engine (CRPE.DLL) shipped with Visual Basic 3.0. If you are a frequent user of Visual Basic and Crystal Reports for Visual Basic it is recommended that the CRW directory be eliminated from your current DOS path. Furthermore, the on-line help files for both version are, in fact, different and therefore, should be kept. There is plenty of documentation within these help files that cannot be found in the Crystal Report Reference Manuals. The CRXLATE.DLL is used in the Crystal Reports function ToWords(X). This DLL is shipped with both Crystal Reports 2.0 and Visual Basic, these DLL's are identical. However, as mentioned above, the DLL from Visual Basic is placed in the WINDOWS SYSTEM directory. The Crystal.VBX that is shipped with Visual Basic is different and a superset of the Crystal.VBX shipped with CRW 2.0. This custom control is invisible at runtime but it still must be distributed with the Visual Basic application. As for the VB.INI, it must be shipped with the distribution disk. VBCOEXIS.DOC $a s w y   ')+2 4   a o q s u w y ӿ0*0*0*0*0*0* 0* T0*0* !$2B +"MOy  y BTimes New Roman Symbol&Arial5Courier New 1Courier"h%Bڥ% m(VB and CRW Coexisting on the same systemTechnical Support DocumentUUse this as a standard format for all the technical support documents to be sent out.Allan D. McMordie Allan Moore