Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Setup

Status
Not open for further replies.

ashishjain

Programmer
Feb 20, 2002
32
0
0
IN
Hi all,
I have developed a software using Visual Basic/Access and crystal Report. I prepared setup using package & Deployment wizard(VS).when i try to install it on fresh machine(Don't have Visual Basic/Access/Crystal Report) it gives "some Crystal32.OCX error" during installation. Which Kind problem this is? How can remove this error?

Regards,

Ashish
 
When packaging you program, when the P&D wizard shows you a list of files required for your program to run, just add the crystal ocx to this list
 
I have a feeling that you can't just add the OCX as it requires a whole bunch of other crystal DLL's. Your best bet is to read the crystal reports documentation. see below for an extract from the documentation (distribution of the report designer).

Hope this helps,

Chris Dukes


Crystal Report Designer Component

The runtime files required to distribute for an application developed using the Crystal Report Designer Component are listed below. These files get installed to the \WINDOWS\SYSTEM (Win95) or \WINDOWS\SYSTEM32 (NT) folder by default, but they can be installed to the application folder.

General Crystal Reports Distribution Files

These files are required to be distributed with any application using any of the Seagate Crystal Reports development tools.

FILE LOCATION DESCRIPTION
IMPLODE.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) Compression Library
SSCSDK32.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) Graphing/Charting dll
CRPAIG32.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) TEXT object dll
CRXLAT32.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) ToWords() function dll
Other Windows files...

FILE LOCATION DESCRIPTION
MSVCRT.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) C Runtime Libraries
MSVCRT20.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) Microsoft Foundation Class Runtime Library
MSVCRT40.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) Microsoft Foundation Class Runtime Library
Crystal Report Designer Components

FILE LOCATION DESCRIPTION
CRAXDRT.DLL \PROGRAM FILES\SEAGATE SOFTWARE\CRYSTAL REPORTS Object Model (Runtime)
CRVIEWER.DLL \PROGRAM FILES\SEAGATE SOFTWARE\CRYSTAL REPORTS Report Viewer
P2SMON.DLL \WINDOWS\SYSTEM or \WINDOWS\SYSTEM32
(NT only) Active Data Driver
Not all files are needed to be distributed for the Report Designer Component. The Report Designer Component is made up of components, allowing only those files being used to be distributed as needed. These dlls need to be registered on the local machine, except for P2SMON.DLL which is not a registering file

n CRAXDRT.DLL gets distributed for every application using the Report Designer Component. This dll has two purposes:

— the reporting engine, and

— exposing the Object Model Hierarchy.

n CRVIEWER.DLL gets distributed if reports are being printed to the screen. If the reports are being exported (see note 2 below) or printed to the printer, and not being viewed to a window, then this dll is not required. Make sure that the MSVFW32.DLL and URLMON.DLL (and SHLWAPI.DLL; dependency for urlmon.dll) are being distributed with this dll.

The dependency dlls are not Crystal files.
n P2SMON.DLL is the Active Data driver. If the reports being distributed are using Active Data (ADO, CDO, DAO, RDO, etc), then this dll must be distributed.

DATABASE DLLs

If the reports are NOT using Active Data, and are using connections (native and/or ODBC) to physical databases, such as Access or SQL Server, refer to the Seagate Crystal Reports, Runtime File Requirements for more information.

EXPORTING DLLs

These dlls are required only if the application is allowing the user to export the report to other formats. Only the dlls distributed will be valid options for the user to distribute. For Example, if only the u2ddisk.dll and u2fcr.dll are distributed, then the only exporting a user is able to do is export to a file on disk, in a Crystal Report format. Refer to the Seagate Crystal Reports, Runtime File Requirements for more information.

User Function Libraries:

If your report contains a formula which uses one of the User Defined Functions (a function listed in the Formula Editor's Additional Functions section), the associated U2XXXXXX.DLL file must be included on the distribution diskette. If the function is one of the Crystal Reports sample User Defined Functions, include the UFLSAMPL1.DLL file. Refer to the Seagate Crystal Reports, Runtime File Requirements for more information.

NOTES:

1. Other files may also need to be distributed, depending on what is being used by the application and the RDC. For example, if the reports being distributed with the application were created using an ADO connection, then there are required ADO files that need to be distributed. Contact vendor for more details. 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..

2. Currently, when exporting a report, any changes made in the SectionFormat() event will not be exported.
 
Thanx some of the file is missing from the list what have given.

Stuff is really helpful.
 
If you reference the OCX in your project, the P&D should pick up all of the satelite Dlls by using the crpe32.dep dependency file - which should be in the Windows/System or where the Crpe32.DLL is.
There is an error in some versions where a manual change of the this dependency file is needed. And there are some issues with the wrong version of Mfc42.Dll which will cause a problem. And many more. I've feel as though I have been through them all and there cannot be any more.
So, report the exact error that you are getting and when it is happening (during installation, near the end of it, after installtion when trying to start the installed program, etc.)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top