My boss wants to know if a dictionary created with Crystal Dictionaries 8.0.0.0 automatically updates when it is opened or accessed to reflect new data added to or old data deleted from linked tables in that dictionary. In addition, I would like to find out if a Crystal 8.5 report placed on an Internet/Intranet Website using Crystal Enterprise 8.0 would work using a Crystal Dictionary, or should an SQL Table/View (SQL Server 7 based) be used instead of Dictionaries? I've heard that there are some problems with trying to use a Crystal Dictionary based Report over the Web in earlier versions of Crystal. Would those problems exist in version 8.5.0.217? Any help in getting the answers would be greatly appreciated. Thank you for your time.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can Crystal Dictionaries 8.0.0.0 be used in Web Based Reporting? 2
- Thread starter scriv1
- Start date
-
1
- #2
HowardHammerman
Instructor
Dictionaries are not affeced by adding data (rows) to your database.
A table view or stored procedures is a better approach.
Howard Hammerman,
Crystal Reports training, consulting, books, training material, software, and support. Scheduled training in 8 cities.
howard@hammerman.com
800-783-2269
A table view or stored procedures is a better approach.
Howard Hammerman,
Crystal Reports training, consulting, books, training material, software, and support. Scheduled training in 8 cities.
howard@hammerman.com
800-783-2269
-
1
- #3
A dictionary doesn't need to 'update' to reflect changes in the data. The dictionaries do not hold any data, just a simplified 'view' of the data. So, if a report uses a dictionary successfully today, it will pick up the data chagnes tomorrow - regardless of how it is launched.
That being said - CD doesn't usually recommend using dictionaries within applications. The problems are usually more with client based apps which have to be configured in different environments but I would try one before you bet the farm on dictionaries. All things being equal I would recommend views.
The one advantage to a dictionary over a view is that with a dictionary the SQL is created based on the tables used in the report - not all of the tables used in the dictonary. This means that you can create reports with fewer tables without getting inflation from the unused tables. A view will always use all tables in the view. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB
tek@kenhamady.com
That being said - CD doesn't usually recommend using dictionaries within applications. The problems are usually more with client based apps which have to be configured in different environments but I would try one before you bet the farm on dictionaries. All things being equal I would recommend views.
The one advantage to a dictionary over a view is that with a dictionary the SQL is created based on the tables used in the report - not all of the tables used in the dictonary. This means that you can create reports with fewer tables without getting inflation from the unused tables. A view will always use all tables in the view. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB
tek@kenhamady.com
- Thread starter
- #4
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question