猝然临之而不惊，无故加之而不怒。
分类：
2004-12-18 11:14:12
我用VB写的一个程序出了点问题,好不容易找以解决方法,备份一下
Err Msg: "Physical Database not found" if using Active Data driver (p2smon.dll)
The information in the article refers to:
Crystal Reports, Report Designer Component 8
Applies to:
Reported version only
Active Data Driver P2smon.dll
Error: "Physical Database not Found"
Synopsis
A report was created using the Crystal Active Data driver (P2smon.dll). When the report was run through an application using one of the Crystal Report Development tools on a client computer, the following error occurs:
"Physical database not found"
Note=========
Crystal Reports development tools include:
-Crystal Report Designer Component Automation server (Craxdrt.dll)
-Crystal Report Engine Automation server (Cpeaut32.dll)
-Crystal Report Print Engine Calls (Crpe32.dll)
-Crystal ActiveX Control (Crystl32.ocx)
-Crystal Visual Component Library (VCL)
=============
Solution
To troubleshoot the error message, try one of the following procedures:
• Ensure that 'p2smon.dll' is in the System32 directory.
• Ensure the following runtime files are installed on the computer:
Msvcrt.dll
Msvcirt.dll
Msvcp60.dll
• Ensure all dependency files for P2smon.dll are on the computer by running the Dependency Walker utility (Depends.exe). Dependency Walker is a free Microsoft utility that scans any 32-bit or 64-bit Windows module, such as *.exe, *.dll, *.ocx, *.sys, etc, and builds a hierarchical tree diagram of all dependent modules.
For further information about Depends.exe, refer to Knowledge Base article c2007141. Search for this Knowledge Base article at .
• Ensure that no other copies of P2smon.dll are being loaded. For example, an older copy of P2smon.dll renamed with any suffix (like P2smon.dll_old) may load and cause errors to appear.
• Ensure the database is not being verified at runtime or at design time.
a) To confirm the database is not being verified at runtime:
Comment out the code that is verifying the database. For example, if you are using the Report Designer Component, you would comment out:
Report.Database.Verify
b) To confirm the database is not being verified at design time:
- Open the report in the Crystal Report Designer.
- On the 'Database' menu, 'Verify on Every Print' should not be checked.
Note: ==========
If you created your report using the Report Designer Component (RDC) in Microsoft Visual Basic (VB), it is an ActiveX Designer report file (DSR). You need to save the DSR file as a Crystal Report file (RPT) so you can confirm if 'Verify On Every Print' is disabled. You can then import that RPT file back into the application.
==============
To save a DSR file as an RPT file:
1. With VB running, open the DSR file.
2. Right-click in an empty area of the DSR file, click 'Report' and then click 'Save to Crystal Reports file'.
3. The 'Save As' dialog box appears. Browse to the folder you want to save the RPT file in, type the name for the RPT file in the 'File Name' box and click 'Save'.
4. The message 'The Crystal Report Designer's event code will not be saved in the report file!' appears.
This message refers to any code in the code window of the DSR file. If the RPT file is imported back into the application, the code can be copied into the new DSR file from the original DSR file.
