Crystal Reports (Version 8.5)(repost)

# Crystal Reports (Version 8.5) This project is for the creation of a two crystal reports. The reports must be created using Crystal Reports Version 8.5. The report will be generated from a database using an ODBC connection. A sample database and an ODBC driver will be provided together with instructions for setting up the driver and database. 1. Report #1: Manager’s Activity Report 2. Report #2: User’s Activity Report The two reports will be identical except the Manager’s Report will show activity for all users while the User’s Activity report will only show their own activity. The report will prompt for two parameters. These parameters will determine what date range is used when querying the database for the information. 1. Start Date 2. End Date ## There will be two sections of the report: **Activities Completed** ??" This section will query the activities table and print a summary of all the activities logged by a user broken down by activity type. For example: User: RMS Phone Call Made 3 Interview Scheduled 2 Email Sent 10 This means that the User ‘RMS’ logged 3 phone call activities, 2 Interview activities and 10 email sent activities. **Records Entered** ??" This section will list all the new records entered by the user. This section will be divided up into * Companies Entered * Candidates Entered * Contacts Entered The name of the record will be listed (e.g. Company Name) with the entry date and the recruited that entered the record. A subtotal will also be printed for each record type (e.g. number of companies entered). There will also need to be a total section that shows the total number of all records entered for that user. ## Deliverables ## Database information: Most of the information will be generated via ODBC to the main database. You will obtain the User Code for the currently logged in user using a second ODBC connection to a flat file database. ### **ODBC Database #1: MJSODBC** **Tables:** 1. [login to view URL] (boolean) 2. [login to view URL] (char 2) 3. [login to view URL] (char 3) 4. [login to view URL] (DateTime) <!-- --> 1. [login to view URL] (char 20) 2. [login to view URL] (char 15) 3. [login to view URL] (boolean) 4. [login to view URL] (boolean) 5. [login to view URL] (Date) 6. [login to view URL] (char 3) <!-- --> 1. [login to view URL] (char 55) 2. [login to view URL] (char 50) 3. [login to view URL] (date) 4. [login to view URL] (char 3) <!-- --> 1. [login to view URL] (char 6) 2. [login to view URL] (int) 3. [login to view URL] (char 35) <!-- --> 1. [login to view URL] (char 12) 2. [login to view URL] (char 18) 3. [login to view URL] (char 3) **Links:** 1. [login to view URL] = [login to view URL] 2. [login to view URL] = [login to view URL] 3. [login to view URL] = [login to view URL] 4. [login to view URL] = [login to view URL] ### ODBC Database #2 - MJSVAR This ODBC connection points to a tab delimited text file containing the user code of the user currently logged in and the location of the database. A sample of this file is as follows: RMS <tab> "C:\SAMPLE DATA\" ### Filters for selects: When querying the activities table, the following filters will be hard coded into the report: [login to view URL] = true [login to view URL] must equal one of the following: F,J,L,@,K,C,N,$,O,T,R,S,E, or P Both the candidates entered and contacts entered sections are generated by querying the FCAND table. A record in the FCAND table is considered a candidate when [login to view URL] = true. It is considered an contact when [login to view URL] = true. Two sample crystal reports that loosly fit the requirements above will also be provided to use as a starting point. ? ? ?