Subject Re: [IBO] IBO 4.0
Author Geoff Worboys
> What is it for and how can I use this properties?
> - SetParamAttribs

If you set this to true then IBO will read parameter column attributes
from the Fields* properties (just as it does for fields). For this to
work well you need to ensure that your parameters are named
differently to your fields.

This was implemented for use with the new ParamName property on the
various controls. If you type the name of a parameter into a controls
ParamName property (no lookup at this stage, so you have to manually
enter the name) then the DataField property will be ignored and the
control will link to the parameter instead. This turns the controls
(including combobox) into parameter editors - and the properties such
as alignment, label etc will be read from the query Fields* properties
if SetParamAttribs is true.

The use of controls as parameter editors is a bit primitive at the
moment, and they are not designed to be quite as dynamic as
TIB_ParamEdit. However it is useful for setting up forms to execute
procedures - where the user can input parameters using edits, combos
and checkboxes.

I expect this feature will be gradually improved as time progresses.

> - TabStopAutomation

Defaults to false. When set to true the control will automatically
set is TabStop property according to whether the associated field is
ReadOnly or Editable. This was setup so that...

In search mode all controls are editable and the user will be able
to tab to all controls.

In editing modes some controls may be readonly so, with
TabStopAutomation set to true, these controls will automatically
remove themselves from the tab list - making more efficient

> Suggestion:
> Add the property PreparedInserts to solve the problems
> with default value, I prefer to use trigges.

Can you please explain what you mean? If you are using triggers to
set defaults (which I also use) then you can simply set
CheckRequired=false to allow the record to be posted without checking.
It is important to realise that ONLY defaults applied in triggers
My_Field = 'Some value';

will work. Defaults defined to the table itself will not be applied.

Geoff Worboys
Telesis Computing