IN API: Option to Support Files and Folders Validation

IN API: Option to Support Files and Folders Validation

The IN API has been enhanced to allow the programmer to specify input as a file or folder.  When this new option is used, F7 will be automatically available to browse for files or folders as appropriate.

Screen Parameters

Comment

IN,rr,cc,ww,tp

t = F indicates this input field is a filename or a folder.  When t = F, p can have the following values:

p = F means the file may or may not exist. Folder portion of the filename must exist.

p = E means the user must input a filename that already exist.

p = W means the file should already exist and a warning will be displayed if a new filename is selected. Folder portion of the filename must exist.

p = N means the file should not already exist and a warning will be displayed if it does. Folder portion of the filename must exist.

p = P means a folder (path) must be input and it may or may not already exist.

p = M means a folder must be input and it must already exist.

 The following rules also will apply:

  • If the user leaves the field blank, no verification will be done and a blank field will be returned to the application program.
  • If a non-required filename is entered (Screen-Type-2 = F or W or N), the folder portion of the filename will be verified and must exist, even though the file does not have to exist.

 Examples:

 IN,04,04,50,FE will enable Browse for File and, when the user attempts to exit the field, the filename selected or typed will be checked, and, if it does not exist, a message will be displayed, and the user will not be able to complete the IN call until an existing file is selected or the field is blanked out.

 IN,04,04,50,FW will enable Browse for File and, when the user attempts to exit the field, the filename selected or typed will be checked, and, if it does not exist, a warning message will be displayed, and the user can move to the next filed.

IN,04,04,50,FP will enable Browse for Folder; the Make New Folder button will be available in the Browse for Folder dialog; and there is no validation of the existence of the selected folder.

IN,04,04,50,FM will enable Browse for Folder; the Make New Folder button will not appear on the Browse for Folder dialog; and the user will not be able to leave the field until an existing folder is selected or the field is blanked out.


 JEG

NWSMSCRN.CBL

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 Developing and Debugging
  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

Feedback and Knowledge Base