[To be completed. Just a sketch with some ideas.]
 
IQ manages fields in the background and there are a few cases where IQ will add data to a field or remove it automatically, depending on certain item manipulation.
 
These automatic field data modification can be classified into 2 categories : 1) those which are hard coded into the system, 2) and those which are specified by the user.
 
 
1- IQ's "hard coded" automatic field data modification
 
The idea here would be to explain what IQ automatically does to fields when :
 
1- an item is added to a grid,
2- an item is moved from one grid to another
3- a subitem is created
4- a subitem is promoted to top level or a TLI is demoted to a lower level
 
 
All that in relationshion to
 
1- simple sources
2- complex sources using the AND operator
3- complex sources using the OR operator
4- complex sources using a mix of operators

etc.
 
  [NOTE : All these should be explained in details so that it's easier for the users to make database design choices in relation to filtering needs. E.g. : should a user use inheritance or not ? A complex source or a simple one ?]
 
 
2. IQ's "user specified" automatic field data modification
 
Fields can be automatically updated, modified, etc. through certain choices of configuration :
  • Field inheritance -- set through the Field management dialog (-- link to nonexistent node ID 1072 -- and ... )
  • "auto assign the following fields"  -- set through the "Manage Grids" dialog's (-- link to nonexistent node ID 896 -- and -- link to nonexistent node ID --)
  • "auto assignment rules" equations  -- set through the Field management dialog ((-- link to nonexistent node ID 1071 -- and Field Management Dialog)
  • SQL requests (and other scripts ?) -- written in the options section of the Field management dialog (Smart Fields and Field Management Dialog)
  • VB scripts written in the VB editor (View -> Visual Basic editor)