(unknown charset) Re: creating text items as runtime in forms 6.0

From: (unknown charset) NinjaToy <LCIYQBBEQVFA_at_spammotel.com>
Date: Tue, 03 Dec 2002 09:23:28 +0000
Message-ID: <3DEC780F.542F774F_at_spammotel.com>


the answer is YES.
if the block were non basetable the block would not fire any of the row level insert / update or delete triggers when commiting the form.

thus, he/she does NOT 'have to manage ALL the database action by himself'. The form will handle all changed record interactions with the database and fire the triggers accordingly.

[Quoted] can I have your reasons as to why how you think this can be done with a non-basetable block?

Luc Bosman wrote:

> On Mon, 02 Dec 2002 18:29:34 +0000, NinjaToy
> <LCIYQBBEQVFA_at_spammotel.com> wrote:
>
> >THIS IS A BASE TABLE BLOCK
> >========================
> >Because you are saving the records to different tables
> >I assume they come from different tables. So this form
> >will be based on a view?
>
> I think it's an enter form only
>
> >This still makes it a base table block.
> >You then need to override the insert, update and
> >delete triggers on the block. With your own.
> >
> >Making it non-basetable will mean forms will not
> >bother trying to save anything to the database.
>
> Yes and no. In the same way, he'll overide insert, update and
> delete triggers on the block, he can overide the key-commit
> trigger. In fact in his situation, he'll have to manage all form
> database action by himself.
>
> --
> Luc Bosman
> DEV/2000 Software Engineer
> Database & Network Administrator
> l.bosman_at_iile.be
>  ----------------------------------------------------
> |  -°)                                          (°-  |
> |  /\\  Linux the choice of the GNU generation  //\  |
> | _\_v                                          v_/_ |
>  ----------------------------------------------------

--
Suzuki SV650S - plop.  Gone.
Kwak ZX-6R J2 - hear the roar
 
Received on Tue Dec 03 2002 - 10:23:28 CET

Original text of this message