Arc Implementation Module Generation

From: Wit Serdakovskij <wit_at_tormoz.net>
Date: Thu, 19 Sep 2002 09:09:40 +0300
Message-ID: <ambpn8$9ut$1_at_hyppo.gu.net>

Good time of day, everyone.

Please review the play and help me find the baby-killer (someone from orchestra-pit).
Actors.
Entities:

Super(S1 - integer, mandatory; S2 - integer; optional);
Sub_A(A1 - integer, mandatory); supertype is Super;
Sub_B(B1 - integer, mandatory); supertype is Super;

Business Function:
Create Sub_A instance(Elementary, Data Entry, Intention to Automate). Usages:
Using Entities: Super, Sub_A (insert);
Using Attributes: A1, S1, S2 (insert).

Scenario.
Our time.
Act 1. Database Design Transformer.Creation of Table Definitions (ARC Implementation). Applouse.
New Actors: Table Definitions: SUPERS, SUB_AS, SUB_BS. Foreign keys in Arc 1 (Mandatory).
Act 2. Design Editor, Server Model. Table Generation, TAPI Generation. Applouse.
Act 3. Object Navigator. Creation of Function Attribute Matrix, Application Design Transforming, Creation of Default Module Data Usages. Applouse.
New Actors: Module TEST0010 (WebPLSQL, Not Candidate). Act 4. Design Editor. Module Generation. Applause. Act 5 (Final). Web browser. Entering values for new Supers record (Fields S1 and S2); "Insert" button pressing..... and .....

Error! Mandatory Arc 1 on SUPERS has not been satisfied.

It's too simple to hurt an artist...
Any help will be accepted.

--
With best regards,
Wit Serdakovskij.

Received on Thu Sep 19 2002 - 08:09:40 CEST