Hi,
It is not Crystal, it is the ODBC drivers and/or differing database structures that do not allow it.
Bring the SqlServer ( Not just SQL, that is a language, not a database) data into Access.
( Or the Access data into SqlServer )
To Paraphrase:"The Help you get is proportional to the Help you give.."
Sure, instead of using Crystal to do this, take the long haul approach, plus improve performance by LINKing the tables into an Access database, either the existing one or creat a new one and link both the current Access DB and the SQL Server db into it.
To do so select New in the tables sectiona nd select Link. Link to the data source (make sure you select save password) and you'll have all of the tables in one Access database.
Now create a query in Access as your Crystal datasource.
This has multiple advantages, not the least of which is that it's available to any tool which can read in an Access database.
Also make sure that you turn on the database show views in Crystal to use an Access Query.
Hi,
Correct - Link for dynamic data that needs to be 'live'.
If periodically extracted data is sufficient, however, actually importing the data on a scheduled basis, may make the report faster..
To Paraphrase:"The Help you get is proportional to the Help you give.."
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.