Steps Required to Test ReportWriter in V8.2

The following steps are required to be able to test Elliott ReportWriter, which is being developed for Elliott v8.3, in Elliott v8.2
  • Copy the RW directory and all its files and subdirectories from M:\Elliott7 to the target root directory (e.g., M:\ELILIP).  (Done)
  • Modify EL800.Cfg in the target \Bin directory.  Add the following sections:  (Done)


Server= is optional.  It defaults to the local computer (environment variable ComputerName).
Root= is optional.  It is the PSQL database name for the root directory, and defaults to ELIROOT.
Company01= is optional.  It is the PSQL database name for Company 01, and defaults to ELI83DATA. 
CompanyNN= entries are optional database names that point to the other companies under the root directory.  They default to ELI83DATAnn.
COMPADDR= is optional.  It names the Company Address image file for displaying on reports and defaults to COMPADDR.PNG.
COMPLOGO= is optional.  It names the Company Logo image file for displaying on reports.  It defaults to COMPLOGO.PNG.

  • Modify EL800S.Cfg in the target \Bin directory.  Add the following sections:  (Done)

ARSTMSCN=Legacy AR Statement
ARSTMENTL=Lipsey's Statement
These entries will result in a selection dialog when the menu item associated with ARSTMSCN is selected.  In this case, the user can select among three options:

ARSTMSCN   Legacy AR Statement
ARSTMENT   Statement
ATSTMENTL  Lipsey's Statement

  • Modify EL800U.Cfg in the target \Bin directory.  This section is optional and is used only to override corresponding selections in EL800S.Cfg.

ARSTMSCN=Legacy AR Statement
ARSTMENT=ReportWriter Statement
  • Create required databases in PSQL ControlCenter.  You need a database like ELI83DATA for each company that will use ReportWriter.  For example, to test Company 96, create a database named ELI83DATA96 (or something else -- this is the default naming convention) and point its dictionary to M:\Elliott7\bin\DDF83 and its data to the appropriate data directory.
  • Set up Images for COMPADDR and COMPLOGO (optional).  If you want an image to appear on the top left of each report page, create a company directory under \RW\Images, like RW\Images\96, and place an image file there.  If the image file is not available, the name and address will appear in its place.
Having made these changes, you will now be able to run both legacy and ReportWriter statements when you select Print Statements from the Control Center.

Developer Documentations

  1. Received Code 9999 with Web Services Call
  2. Received Return Status Code 3 When Using Elilogin Login Method
  3. Elliott Web Service Requirements
  4. Elliott eStore Checklist
  5. LN API
  6. FN API
  7. RN API
  8. IN and DF API Change (V9.0)
  9. FA API Changes (V9.0)
  10. VA API Changes (V9.0)
  11. CartService
  12. EliarachService
  13. ElicshtxService
  14. EliattrbService
  15. ElisyscdService
  16. EliNoteService
  17. El2rstimService
  18. EliOrderService
  19. ItemInquiry
  20. EliitmiqService
  21. EliShiptoService
  22. El2getfrService
  23. Steps Required to Test ReportWriter in V8.2
  24. Installation of ElliottService, NETcellent’s Web Services for Elliott
  25. ResellerFinder
  26. EliaptrxService
  27. VendorInquiry
  28. EliloginService
  29. ElislsmnService
  30. EliserhsService
  31. EliatpobService
  32. ElievprcService
  33. ElihdtrxService
  34. ElicuswlService
  35. QueryTurnaround
  36. InvoiceInquiry
  37. ElicustmService
  38. EligetcdService
  39. OrderInquiry
  40. EliordiqService
  41. EliecontService
  42. EliautdpService
  43. El2CrCrdService
  44. Log-Timer / ElliottTimer.Ini Support
  45. Alpha Document Number Support (V8.5/V9.0)
  46. ElliottService System.TypeInitializationException
  47. Feature - Printing API to Dynamically Set Number of Copies
  48. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  49. DD API Changes (V9.0)
  50. PA API (8.5)
  51. Validate License API
  52. AP API
  53. TP API: Temporary Path
  54. Data Structures for Report Desk Defaults and Enforcements
  55. COBOL to VB Interface Programs
  56. IN API: Option to Support Files and Folders Validation
  57. FF API: File Functions
  58. ID API
  59. LK: Links API
  60. FFLNearYou
  61. Report Desk: Registry Settings
  62. Developing a New Elliott V8.6 Report Desk User Defined Report (UDR)
  63. CustomerInquiry
  64. Elliott API (JSON Web Service)
  65. Animating COBOL Code in Elliott V8.5
  66. Preliminary Programming Changes for Elliott 8.6
  67. CV API
  68. System Lock File Requirements
  69. How to Write Test Codes for C# ESS Projects
  70. Solving the Inability to Debug Elliott on a New Server
  71. Report Desk: Developing Custom Reports
  72. Report Desk Tables
  73. Report Desk Database Delivery Strategy
  74. Logging I-O Logic Errors
  75. Report Desk: Developer Documentation Roadmap
  76. Report Desk: Resolution of Pervasive.Data.SqlClient.dll
  77. TB API
  78. Creating HTML Emails for Professional Presentation
  79. EM API - Create and Send an Email
  80. DN API (Document Number Handling)

Feedback and Knowledge Base