[RBASE-L] - Re: EEP School

[Bruce Chitiea]

Bill:

Thanks so much. Precisely the structured response needed. I hope the post continues ... we'll end up with a mini-manual.

Yours,

Bruce

-------- Original Message --------
Subject: [RBASE-L] - Re: EEP School
From: Bill Downall <bdown...@downallconsulting.com>
Date: Tue, June 12, 2012 1:47 pm
To: rbase-l@rbase.com (RBASE-L Mailing List)

Bruce,

I'll bet you have opened a long conversation with a lot of contributors.

Here are some design ideas:

On before start:

• Initialize all variables to be used in form (Including looking up of any constants or defaults)
• Create any temporary tables or views to be used for lookup controls, etc.
• (PROPERTY commands will not work here, because no component IDs or custom form actions will have been instantiated   "before start")

On After Start:

• Property commands to initialize look and feel
• adjust initial form and control sizes to monitor dimensions,
• ENABLED 'false' for controls that should not yet be active

Custom Form Actions:

• typically named "on<eventname>", e.g. "OnChooseCustomer", and do variable settings, lookups and form changes that need to be reset only when the user does something that changes an important value

On Close

• clear form-only variable
• any inserts to log tables

I haven't used the on resize or on roll-up / roll-down very much, but I do find row eeps important, under Tables / Table Settings:

• On Row Entry
• On Row Exit
• etc.

Bill

On Tue, Jun 12, 2012 at 4:25 PM, Bruce Chitiea <rby...@safesectors.com> wrote:

All:

Is there a simple, articulated design 'philosophy' or rule-set governing the choice of what is to be included, or excluded from each of the Form EEP classes:

- On Before Start

- On After Start

- On Close

- On Resize

- On Roll Up

- On Roll Down

I'm working my way slowly through the RRBYW17 samples and will probably 'get it' in the end; but all assistance appreciated.

Bruce