Subject | Re: IB_Grid and Stored Procedure |
---|---|
Author | Svein Erling |
Post date | 2003-11-13T11:23:41Z |
--- In IBObjects@yahoogroups.com, "ronald_greven" <rs@s...> wrote:
property of the IB_Query you use to select from the stored procedure.
components, but cannot return several records and ought not to be used
with selects.
IB_Cursors are unidirectional, and what is preferable if you select
from a table. The exception being if you need a bidirectional dataset
(i.e. possibility to scroll back and forward), then IB_Query is your
only option.
Set
> Hello,Forget the data grid, and focus on the data source. Use the EditSQL
>
> I have a big problem again :
>
> I am using a IB_Grid, where I display data from a stored procedure.
> Now I want to edit only one field and write it back to another
> table.
>
> For example :
>
> Grid : (Data from Stored Procedure)
> Pos Amount ...
> 1 5 <--- write it to table x
> 2 0 <--- don't write
> 3 4 <--- write it to table x
>
> how can I realise this?
>
> And which properties do I have to change, that it is possible, to
> edit data in the grid, if the datasource is a stored procedure?
> (Grid changes to edit mode, but no input is possible)
property of the IB_Query you use to select from the stored procedure.
> And another question?Use IB_DSQL for inserts, update etc. It is the fastest of the three
> Could somebody tell me the difference between, IB_Query, IB_Cursor
> and IB_DSQL? (With each of them, its possible, to execute the same
> SQL's)
components, but cannot return several records and ought not to be used
with selects.
IB_Cursors are unidirectional, and what is preferable if you select
from a table. The exception being if you need a bidirectional dataset
(i.e. possibility to scroll back and forward), then IB_Query is your
only option.
Set