Subject | Re: [IBO] Set a TIB_Query into dssEdit mode |
---|---|
Author | Helen Borrie |
Post date | 2002-09-21T07:20:37Z |
At 09:00 AM 21-09-02 +0200, you wrote:
provided your dataset is updatable (in SQL terms). If a dataset is
updatable then simply setting RequestLive to True will make editing
available - provided your KeyLinks are correct.
If not (i.e. you have a joined dataset and you want to operate on multiple
tables) you still can make your dataset "live" (updatable) by providing SQL
statements in the InsertSQL, EditSQL and DeleteSQL properties. As a
general rule, these statements will be EXECUTE calls to stored procedures
which accept your dataset's KeyLinks as separate input parameters (along
with any other parameters you want to pass...)
Helen
>I'm not sure that I understand what you mean with 'UpdateSQL statement'. InIBO does update and insert and implicitly for you in the background,
>my TIB_Query mostly a 'select * from Table_xy', maybe in some queries with a
>'where...' for filtering, is working. I know there is an UPDATE statement,
>but when should I use it? Or is it only one more possibility to do it?
>
>Or is that what IBO is doing implicit for me in the background?
provided your dataset is updatable (in SQL terms). If a dataset is
updatable then simply setting RequestLive to True will make editing
available - provided your KeyLinks are correct.
If not (i.e. you have a joined dataset and you want to operate on multiple
tables) you still can make your dataset "live" (updatable) by providing SQL
statements in the InsertSQL, EditSQL and DeleteSQL properties. As a
general rule, these statements will be EXECUTE calls to stored procedures
which accept your dataset's KeyLinks as separate input parameters (along
with any other parameters you want to pass...)
Helen