Requirements: Difference between revisions

From Crystal Manager for Sage CRM
No edit summary
No edit summary
Line 1: Line 1:
*Sage CRM 6.2, 7.0 or 7.1
*Sage CRM 6.2, 7.0,7.1, 7.2
*DB: MSSQL (Enterprise/Express) only
*CRM DB: MSSQL  
*Crystal Run-time - CRRuntime_32bit_13_0_1.msi (shipped with the product)
*Crystal Run-time - CRRuntime_32bit_13_0_1.msi (shipped with the product)
*Crystal Reports - To create the reports (not required on the server)
*Crystal Reports - To create the reports (not required on the server)
*.Net 3.5 and .Net 4.0 framework installed on server
*.Net 3.5 and .Net 4.0 framework installed on server
   
   
 
*Note: If you are running pre 7.2 - Sage's native Crystal Reports Integration (pre 7.2 as support ended then) and Crystal Manager cannot run on the one server at the same time!
*Note: Both Sage's Crystal Reports Integration (pre 7.2 as support ended then) and Crystal Manager cannot run on the one server at the same time!


----
----
Note: The Crystal Report Engine that is shipped with our software allows 3 reports to be executed at any one time. Reports are queued then.
Note: The Crystal Report Engine that is shipped with our software allows 3 reports to be executed at any one time. Reports are queued then. This is sufficient for most businesses and no locking up occurs.

Revision as of 11:34, 28 March 2014

  • Sage CRM 6.2, 7.0,7.1, 7.2
  • CRM DB: MSSQL
  • Crystal Run-time - CRRuntime_32bit_13_0_1.msi (shipped with the product)
  • Crystal Reports - To create the reports (not required on the server)
  • .Net 3.5 and .Net 4.0 framework installed on server
  • Note: If you are running pre 7.2 - Sage's native Crystal Reports Integration (pre 7.2 as support ended then) and Crystal Manager cannot run on the one server at the same time!

Note: The Crystal Report Engine that is shipped with our software allows 3 reports to be executed at any one time. Reports are queued then. This is sufficient for most businesses and no locking up occurs.