Subject | Re: [IBO] Two or more tables... |
---|---|
Author | Helen Borrie |
Post date | 2005-12-05T00:54:19Z |
At 04:19 PM 4/12/2005 -0800, you wrote:
(not scrollable, and opened at BOF)and for the master set to be required to
fetch each row individually. So (after all this terrible confusion), the
reason you don't see any rows is that your master set can't call Fetch in
the scroll event! You need a scrollable dataset for master/detail to work
as designed.
Who told you to use "FOR UPDATE"? IBO itself encapsulates this attribute
in the tib_cursor. Contrary to some people's assumptions, the "FOR UPDATE"
attribute is not some shortcut means to make datasets updatable!
Also, get rid of the practice of using SELECT *. It's a lazy habit that
makes your source code less informative than it ought to be and it also has
some undesirable effects in the interface, under some conditions, that can
be very difficult to track down.
Helen
>Take out "FOR UPDATE". This will cause the detail set to be unidirectional
> in the PATOLOGIAtib_query i have:
>
> SELECT *
>FROM PATOLOGIA
>FOR UPDATE
> _______________________
(not scrollable, and opened at BOF)and for the master set to be required to
fetch each row individually. So (after all this terrible confusion), the
reason you don't see any rows is that your master set can't call Fetch in
the scroll event! You need a scrollable dataset for master/detail to work
as designed.
Who told you to use "FOR UPDATE"? IBO itself encapsulates this attribute
in the tib_cursor. Contrary to some people's assumptions, the "FOR UPDATE"
attribute is not some shortcut means to make datasets updatable!
Also, get rid of the practice of using SELECT *. It's a lazy habit that
makes your source code less informative than it ought to be and it also has
some undesirable effects in the interface, under some conditions, that can
be very difficult to track down.
Helen