Does anyone has positive experience with connecting CrystalReports on two SQL server databases.
Clarion needs to connect to traffic , yearly data in first database , and linked table is in another SQL server database.
I already have experience with CrystalReports and ODBC connectors through CrystalClear class.
Any guide or example ?
I would do this on the server. Write a view or stored procedure on SQL server database 1 that joins the data from both databases however is required. Then use Crystal to access that view/store proc.
Keeps the double connection complexity out of Crystalâs side of things.
Elegant solution for new project . In our case , there are hundreds Crystal reports . We thought , in report call to after " SetAllTablesLogOnInfo " cheaply redirect one table to "SetTableLogOnInfo(âLinkedTableâ,clip(GLO:server),clip(GLO:database),clip(GLO:user),clip(GLO:PASSWORD2),true) ".
There is old one OCX topic
?CrystalControl{âReportFileNameâ}=vsu3.getexepath() & âtest00.rptâ
! ne valja ?CrystalControl{âPrintFileNameâ}=vsu3.getexepath() & âtest00.rptâ
?CrystalControl{âWindowStateâ}=2
?CrystalControl{âWindowControlsâ}=true
?CrystalControl{âWindowControlBoxâ}=true
?CrystalControl{âWindowAllowDrillDownâ}=true
?CrystalControl{âWindowShowRefreshBtnâ}=true
?CrystalControl{âWindowShowSearchBtnâ}=true
?CrystalControl{âWindowShowPrintSetupBtnâ}=true
?CrystalControl{âWindowShowGroupTreeâ}=true
?CrystalControl{âProgressDialogâ}=True
?CrystalControl{âDestinationâ}=0 !0=window
?CrystalControl{âDiscardSavedDataâ}=1
?CrystalControl{âCopiestoPrinterâ}=1 !Copies
X#=?CrystalControl{âPrintReportâ}
It works with flat tables , but donât have full set of properties ( SQL Server and ODBC) .
May be someone has whole list ?