Newsgroup: it.comp.lang.visual-basic
Titolo: Setup VB6 e Crystal Report 8.5

Ho una procedura scritta in VB6 che utilizza il Crystal Report 8.5, e
visualizza le stampe con CrViewer.DLL. Generando il setup standard VB6 ed
installando l'applicazione su un altro pc, mi dà un errore in fase di
registrazione procedura. Eseguendolo, di stampe non se ne parla. Sapete cosa
si deve inserire manualmente nel Setup? Attualmente ho risolto il problema
installando CR8.5 anche nell'altro PC. Grazie. Benedetto.

 ha scritto nel messaggio
news:tIUC9.34392$744.1...@news1.tin.it...
Cito dalla Kb di Seagate (c2008905)
(poi mi dite che sono "scorbutico" perchè la gente non guarda mai l'help...)
Runtime File Requirements for the Report Designer Component version 8.5
The information in the article refers to:
Report Designer Component 8.5
Applies to:
Reported version only
Distribution
Runtime File Requirements
Synopsis
What runtime files do you need to distribute with your application when
using the Report Designer Component (RDC) version 8.5 as the reporting
development tool?
Solution
The runtime files you require to distribute an application developed using
the Report Designer Component (RDC) are listed below. These files are
installed to the \Windows\System (Microsoft Windows 9x) folder by default,
however you can also install them to the application folder.
The Crystal Reports runtime files required for distribution with your
application are dependent on the following:
- The method used to access the Crystal Report Engine.
- The data source your reports use.
- The exporting options you want available to end-users.
- Any additional components you may be using such as charts, maps,
additional formula language functions, and so on.
When using the RDC version 8.5 there are four main components:
- Craxdrt.dll - The Crystal Reports 8.5 ActiveX Designer Runtime DLL. This
DLL is the reporting engine and it exposes the Object Model Hierarchy.
Distribute this DLL with all applications using the RDC.
- CRViewer.dll - The Crystal Reports View Control. Use this component to
preview your report. If you are not previewing the report, then it is not
necessary to distribute this DLL.
- CRDesignerCtrl.dll - Embeddable Crystal Reports 8.5 Designer Control. This
DLL is new to Crystal Reports 8.5. This DLL exposes report creation and
designer capabilities in your application and allows you to create a report
at runtime using an ActiveX designer.
- Craxddrt.dll - Crystal Reports 8.5 ActiveX Designer Design and Runtime
DLL. This DLL is new to Crystal Reports 8.5. This DLL is the engine used to
design and format reports at design time, as well as to access and process
reports at runtime.
Not all of these DLLs need to be distributed with your application. Only
distribute these DLLs if you use them in your application. For example, if
you do not use the Embeddable Designer Control, then you would not
distribute CRDesignerCtrl.dll and Craxddrt.dll.
For a listing of the dependency files for the Report Designer Component and
the Embeddable Crystal Reports Designer Control, refer to 'Runtime.hlp' and
look under 'Method Used to Access the Crystal Report Engine'.
Note: =======
In addition to the dependency files listed in 'Runtime.hlp', the four main
components of the RDC also require these dependency files:
Craxdrt.dll: Mfc42.dll, Msvcrt.dll, Msvcp60.dll, Comdlg32.dll, Comctl32.dll
CRViewer.dll: Comctl32.dll
CRDesignerCtrl.dll: Msvcrt.dll, Comctl32.dll
Craxddrt.dll: Mfc42.dll, Msvcrt.dll, Msvcp60.dll, Comctl32.dll,
Comdlg32.dll, Msvcirt.dll
============
ACTIVE DATA
If your reports use Active Data (ADO, CDO, DAO, RDO, etc) you need to
distribute the Active Data driver, P2smon.dll (plus its dependencies).
P2smon.dll is dependent upon the following files:
Msvcirt.dll
Msvcp60.dll
Msvcrt.dll
DATABASE DLLs
If the reports are not using Active Data and are using connections (native,
ODBC, or OLE DB) to physical databases (such as Microsoft Access or SQL
Server), refer to 'Runtime.hlp' and look under 'Data Access' for more
information.
EXPORTING DLLs
Distribute these DLLs if your application has exporting functionality. Only
those DLLs distributed will be valid options for exporting. For example, if
only U2ddisk.dll and U2fcr.dll are distributed, then you can only export a
report to a file disk in a Crystal Report format.
Refer to 'Runtime.hlp' and look under 'Exporting' for more information.
USER FUNCTION LIBRARIES (UFL)
If your report uses a User Defined Functions (a function listed in the
Formula Editor's Additional Functions section), then the associated
U2xxxxx.dll (UFL) file must be included in the distribution. If the function
is one of the Crystal Reports sample User Defined Functions, include the
Uflsampl1.dll file.
Refer to 'Runtime.hlp' and look under 'Additional Components' then 'User
Function Libraries' for more information.
Note: ========
- Other DLLs that a Crystal report may use and need to be distributed are:
ODBC files, RDO/DAO/CDO files, OLE DB core & providers, SQL Server/Oracle
clients, Access (DAO/JET) files/engines, etc.
- For further information about runtime file requirements for the RDC go to
http://support.crystaldecisions.net/kbase
 and search for articles C2007290
and C2002369.
ciao
ugo