Client Connectivity

[sandra]

I have heard somewhere that there is something in Crystal Reports called "Client Connectivity". It should be installed on the client pc's.
When I have a VB application installed on my server, I should have the Crystal Reports Client Connectivity in stalled on the workstations. It allows the reports to have a link with the SQL server.

Does anyone have any idea about this?
And if he does, where can I get it from? Why can't I see it on my Crystal Report installation CD?

[ARPRINCE]

I think "client connectivity" refers to an ODBC connection to the SQL server (or any database external to the client machine).

The ODBC data source is the object that you connect to when accessing data with Crystal Reports. So if your client wants to run a VB application w/ CR installed in a server, the client must have the ODBC connection to be able to access both the SQL Server and the CR Reports.

Remember, when you design your CR, you are given several options on how to connect to the database (DAO, ODBC, OLAP, OLE DB, etc.). Most of the time for SQL (I believe), we use either ODBC or OLE DB (see sample below coded in VB to access the table in a SQL database).

   With crxReport.Database.Tables(1).ConnectionProperties
      .Item("Provider") = "SQLOLEDB"
      .Item("Data source") = "SRV_SQL"
      .Item("Initial Catalog") = "NEWACCOUNT"
      .Item("User ID") = "ADMIN"
      .Item("Password") = "SHOWMETHEMONEY"
   End With

[valentindvf]

How can subreports I make the same with subreports?

Thanks

[brucevde]

There should be a help file in your crystal report directory, called Runtime.hlp. It contains information regarding what needs to be installed on the client pc in order for the VB applications to use Crystal reports.

Client Connectivity also means that you need to install the required database dlls. For instance, if your db is Oracle, you need to install the Oracle Client (from your oracle cds). If your db is SQL Server you need the sql server dlls.