Crystal Reports bug when connecting via ODBC to 2 different datasources
You might try attaching the MS SQL tables to the MS Access database (File |
Get External Data | Link Tables) and then do all of you reporting against
the Access database, changing table references as as needed. As long as you
have the ODBC driver, you can attach any database table to an Access
database (Oracle, MS SQL, etc.)
I'm an on-again, off-again Crystal user (depends on the client) but I am
amazed at the number of submissions from people who use have/use MS Access
as a database and then turn to Crystal Reports do to reporting when Access
has a fairly nice reporting tool itself. And you can reuse Access queries
in many reports.
Also, I've seen a new control that allows you to print Access Reports from
within VB.
Quote:
>Hi,
>I'm using NT4.0 (service pack 3) , VB5 and CR6.0 . The application I've
>written fires off crystal reports which retrieves data from an external
ODBC
>datasource (either MS Access or MS SQL Server).
>The problem I'm having is that if I originally create the .rpt file
pointing
>at an Access data source the
>.rpt file displays integer values incorrectly if at runtime the ODBC data
>source is MS SQL Server (and vice versa). I don't want to have to ship two
>versions of the .rpt file (one for access, one for sql server) with the VB
>app. What can I do? Thank you.
