Baanboard.com

Go Back   Baanboard.com

User login

Frontpage Sponsor

Main

Google search


Poll
How big is your Baan-DB (just Data AND Indexes)
0 - 200 GB
18%
200 - 500 GB
26%
500 - 800 GB
3%
800 - 1200 GB
9%
1200 - 1500 GB
12%
1500 - 2000 GB
12%
> 2000 GB
21%
Total votes: 34

Baanboard at LinkedIn


Reference Content

 
4GL main table i/o sections
By patvdv at 26 Feb 2008 - 21:56

4GL main table i/o sections

Note that main.table.io sections (except the read.view subsection) are ignored when the corresponding DAL hooks are programmed in a DAL script.

You use main table i/o sections to program actions that you want to be executed when read or write actions occur on the main table. These sections are not relevant to type 4 programs, as such programs do not have a main table. Main table i/o sections consist of a main section and a subsection. The main section is always main.table.io. The subsection indicates when the actions must be executed.

Main section

main.table.io:

The subsections associated with this main section are executed either before or after input to or output from the main table. The main table for the current session is defined in the data dictionary.

Subsections

read.view:

The actions programmed in this subsection are executed immediately after a view action on the main table (start.set, first.view, next.view, prev.view or last.view). You can use this subsection to call skip.io() in order to skip an entire set of records with the same value in the view fields.

before.read:

The actions programmed in this subsection are executed immediately before each read action on the main table.

after.read:

The actions programmed in this subsection are executed after each read action on the main table. You can use this subsection to call skip.io() in order to skip the record just read and to read the next record (if necessary).

before.write: and before.rewrite:

The actions programmed in this subsection are executed before each (re)write action on the main table. A write action occurs when a record is inserted. A rewrite action occurs when a record is changed. You can use this subsection to call skip.io() in order to undo the (re)write action.

after.write:

The actions programmed in this subsection are executed after each (re)write action on the main table. A write action occurs when a record is inserted. A rewrite action occurs when a record is changed. You can use this subsection, for example, to write data to tables other than the main table.

after.skip.write: and after.skip.rewrite:

The actions programmed in these subsection are executed if a (re)write action on the main table has been skipped as a result of actions programmed in the before.(re)write subsection. The actions are executed immediately after the skip action.

before.delete:

The actions programmed in this subsection are executed immediately before each delete action on the main table. You can use this section to call skip.io() in order to skip the delete action.

after.delete:

The actions programmed in this subsection are executed immediately after each delete action on the main table. You can use this subsection, for example, for deleting references, if this is not done automatically.

after.skip.delete:

The actions programmed in this subsection are executed if a delete action on the main table has been skipped as a result of actions programmed in the before.delete subsection. The actions are executed immediately after the skip action.

Example

 main.table.io:
 read.view:
  if strip$(pctst099.cprj) = "" then
    skip.io("")
  endif

Related help topics


0
No votes yet


All times are GMT +2. The time now is 05:06.


©2001-2018 - Baanboard.com - Baanforums.com