Table Browser and Verifile (None Specified)
At 20 NOV 1999 07:03:47PM Jo Peoples wrote:
Like many who are migrating an app from AREV to OI, I am often looking for equivalents or find discrepancies. Two cases in point:
1. In AREV switching between form view and table view was a useful option. However, in OI the table browser is a 'legacy feature', though it is accessible and can be used for quick queries. Is the idea one should always use the Report Designer? One of the greatest features of AREV was the TCL to do quick 'select' or 'list' queries allowing you to print an ad-hoc list on the fly: much quicker than using the Report Designer. Also the table browser cannot be searched by symbolic field which is a real downer.
2. When using "verifile" (which is not documented in the help files) to validate entries, it will only work if the @ID is entered. I used to be able to specify or use another column in the table to 'verify' against. Is this possible in OI?
At 22 NOV 1999 11:31AM Donald Bakke wrote:
Jo,
1. Ad-hoc queries and reports are possible in OI, but the tools that come natively with OI are not very good. S/List is a good tool to use, even if you just created your own interface and passed the LIST or SELECT statement through the provided SLIST subroutine. Keep in mind, however, that with Revelation's licensing policy you need to have a developer system, development-ready SDP, or the new Reporting license to use a tool like this.
2. I am not certain how you are using VERIFILE in your example. Are you verifying against another column in the same record or are you verifying the key against the same table, i.e., preventing the user from entering a new record this way? The latter is done by applying a standard verifile against the key control. If a built-in solution won't help with the former then you can always write a custom routine to do this for you.
