|
|
|
|
|
|
|
|
Dicas
|
|
|
Visual Basic (Crystal Reports)
|
|
 |
Título da Dica: Solução da instalação com o crystal 9.0
|
 |
|
|
|
Postada em 2/2/2004 por ~Ð@®£@Ñ
Vou passar o texto do artigo, se você seguir certinho não dá erro apesar de ser trabalhoso. Se você quiser posso tentar disponibilizar esse Setup.
============================================================
faça o seguinte e nessa ordem.
dentro da pasta "arquivo de programas\arquivos comuns" crie o diretório "crystal decisions\2.0\bin".
copie o arquivo "cr9deploy.reg" para o diretório criado.
altere o conteúdo do arquivo para o diretório "arquivo de programas\arquivos comuns\crystal decisions\2.0\bin" que você criou. após a alteração, execute o arquivo e depois clique em 'sim'.
dentro desse mesmo diretório copie os seguintes as arquivos.
UNICOWS.dll
*craxdrt9.dll
querybuilder.dll
ufmanager.dll
atl.dll
**implode.dll
*crqe.dll
*keycode.dll
*crviewer9.dll
*registre com o utilitário regsvr32
**necessário para relatórios criados nas versões anteriores do crystal
os arquivos de acesso a dados tem os nomes iniciados em crdb_*.dll ou p2*.dll. se você usa o ado, você deve copiar para esse diretório o arquivo "crdb_ado.dll"
espero ter ajudado. consegui instalar, depois que o fábio cr, um colega nosso aqui do fórum, me passou o seguinte texto.
============================================================
the runtime files you require to distribute an application developed using the rdc are listed below.
============================================================
note:
crystal reports components now support side-by-side installation. this type of installation allows multiple versions of previously shared dlls to be installed on the same machine.
the dlls are isolated on the machine allowing applications that require different versions of the same shared dll to be installed on the same machine. you could have an application using version 9 of the report designer component (rdc) running on the same machine as an application using a previous version of the rdc.
============================================================
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 9 there are four main components:
- craxdrt9.dll - the crystal reports 9 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.
- crviewer9.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 9 designer control. this dll exposes report creation and designer capabilities in your application and allows you to create a report at runtime using an activex designer.
- craxddrt9.dll - crystal reports 9 activex designer design and runtime dll. 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 do not distribute crdesignerctrl.dll and craxddrt9.dll.
for a listing of the dependency files for the report designer component and the embeddable crystal reports designer control, refer to 'runtime.chm' and look under 'method used to access the crystal report engine'.
============================================================
note:
in addition to the dependency files listed in 'runtime.chm', the four main components of the rdc also require these dependency files:
craxdrt9.dll: mfc42.dll, msvcrt.dll, msvcp60.dll, comdlg32.dll, comctl32.dll
crviewer9.dll: comctl32.dll
crdesignerctrl.dll: msvcrt.dll, comctl32.dll
craxddrt9.dll: mfc42.dll, msvcrt.dll, msvcp60.dll, comctl32.dll, comdlg32.dll, msvcirt.dll
============================================================
steps required to allow printing of a report through an application (no viewing):
- microsoft dependency files that must be in place
-- mfc42.dll (version 6.0.8447.0 or higher)
-- msvcrt.dll (version 6.0.8397.0 or higher)
-- msvcp60.dll (version 6.0.8168.0 or higher)
- other dependency files (to be placed in the <%systemroot%>\system32 folder)
-- comdlg32.dll
-- comctl32.dll
-- riched20.dll
-- usp10.dll
- crystal runtime files that need to be installed (recommended to install in this order)
-- run cr9deploy.reg; (or modify this file to where you will have your bin folder, the rest of this article assumes that the bin folder location is "c:\program files\common files\crystal decisions\2.0\bin") refer to 'runtime.chm' and look under 'side-by-side installation' for more information.
-- copy UNICOWS.dll to "c:\program files\common files\crystal decisions\2.0\bin". include UNICOWS.dll (version 1.0.3703.0 or higher) into distributions that are targeted for windows 9x computers. for more information, refer to knowledge base article c2011871
-- copy craxdrt9.dll to "c:\program files\common files\crystal decisions\2.0\bin" (register this file using regsvr32.exe)
-- copy the following dependency files to "c:\program files\common files\crystal decisions\2.0\bin"
--- implode.dll (for applications using reports created in versions previous to crystal reports 8)
--- querybuilder.dll
--- ufmanager.dll
--- atl.dll (there are two versions of atl.dll one for win9x and another for winnt/win2000. please refer to special instructions in 'runtime.chm' and look under 'additional components' and then 'paged-ranged export' for more information.)
-- copy crqe.dll to "c:\program files\common files\crystal decisions\2.0\bin" (register this file using regsvr32.exe)
-- copy keycode.dll to "c:\program files\common files\crystal decisions\2.0\bin" (register this file using regsvr32.exe)
steps required to allow viewing of a report in an application (to be added to the previous steps):
- copy crviewer9.dll to "c:\program files\common files\crystal decisions\2.0\bin" (register this file using regsvr32.exe)
steps required to allow the embeddable designer to work (to be added to the previous steps):
- copy crdesignerctrl.dll to "c:\program files\common files\crystal decisions\2.0\bin" (register this file using regsvr32.exe)
- copy craxddrt.dll to "c:\program files\common files\crystal decisions\2.0\bin" (register this file using regsvr32.exe)
active data
if your reports use active data (ado, cdo, dao, rdo, etc) you need to distribute the correct active data driver. refer to 'runtime.chm' and look under 'database access' then 'active data' for more information.
database dlls
if the reports are not using active data and are connectioning (native, odbc, or ole db) to physical databases (such as microsoft access or sql server), refer to 'runtime.chm' and look under 'database access' for more information. database dll names start with crdb_*.dll or p2*.dll.
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.chm' and look under 'exporting' for more information.
============================================================
note:
exporting to html
to export to html format you must include these runtime files in the "c:\program files\common files\crystal decisions\2.0\bin" folder:
-- crxf_html.dll
-- reportrenderer.dll (register this file using regsvr32.exe)
-- pageobjectmodel.dll (register this file using regsvr32.exe)
-- webreporting.dll (register this file using regsvr32.exe)
-- commonobjmodel.dll (register this file using regsvr32.exe)
-- rptdefmodel.dll (register this file using regsvr32.exe)
-- u2fcompress.dll
-- gdiplus.dll (due to licensing restrictions, you must get gdiplus.dll from the microsoft web site. go to http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdkredist.htm and select "gdi+ rtm").
the report engine merge module includes
-- crxf_html.dll
-- reportrenderer.dll
-- pageobjectmodel.dll
-- webreporting.dll
you will need to add the following files to your install package manually in order to succesfully permit exporting to html:
-- u2fcompress.dll
-- commonobjmodel.dll
-- rptdefmodel.dll
-- gdiplus.dll
if you are missing a file, then you will receive the error message: run-time error '-2147190908 (80047784): failed to export the report"
============================================================
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 u2*.dll (ufl) file must be included in the distribution.
refer to 'runtime.chm' and look under 'additional components' then 'user function libraries' for more information.
============================================================
note:
other dlls that a crystal report may use (and need to distribute) include:
odbc files, rdo/dao/cdo files, ole db core & providers, sql server/oracle clients, access (dao/jet) files/engines.
============================================================
Original: Caco
|
|
|
|
|
