GUI principals - design forms for add new record, modify record

[SÁRINGER Zoltán]

Hello,

When you want to create/modify master-detail records, what are the most
practical ways? (For example: having partners, and each partner has some
sites, contacts, discount prices.. etc)

I know two methods, please complete the variatons of yours:

1) press "new": read and edit all data, related data in the memory. When
press "save", begin transaction, save master table, and save the details
table. Problem is to check what records were added/modified/deleted in
master tables, but seems simple for the user (one press save...) Also, it
takes long time to refresh all the detail tables.. mostly via internet..

2) press "new": first of all, a little window asks for basic data, such as
"name". Then creates it in the master table, and open the form as "modify"
view. Each detail table has bound to database directly, user can
delete/insert/modify the records directly. "Save" button saves only the
chages of master table.

....and tell me, what solution do you suggest, the point of views are:
- work fast via internet, (minimalize the roundtrips)
- convinient to the user
- easy to code and maintain

thank you!

 

[David Portas]

Use stored procedures to handle the modifications rather than trying to
update the tables directly.

 

[John Bell]

Hi

You should present the two designs to your users and let them decide! It may
be that they do not have all the details at hand when the initially enter
the master information, therefore option 2 may fit their work patern better.
If option one fits their work pattern better then it should be the most
efficient way for them to input the data, but if you implement option 2 when
this is the case, then you may end up making them less productive and they
will cuss the system you have written!

- work fast via internet, (minimalize the roundtrips)

Whatever system you implement the use stored procedures should minimise
round trips and it should help you avoid SQL injection if you use strict
typing.

- convinient to the user

This is more to do with layout, putting fields in the logical order,
(possibly) give them templates or defaults, avoid excessive mouse
intervention, make sure that your form can be accessible by persons with
different abilities, make your process "intuative" and the workflow flows.
Make sure that information is logically grouped and you avoid information
overload and clutter.

- easy to code and maintain

Use of stored procedure should help this, use of templates so forms have a
common structure, use of meaningful comments and good documention.

John

 

[Ralph]

Hi

You should present the two designs to your users and let them decide! It may
be that they do not have all the details at hand when the initially enter
the master information, therefore option 2 may fit their work patern better.
If option one fits their work pattern better then it should be the most
efficient way for them to input the data, but if you implement option 2 when
this is the case, then you may end up making them less productive and they
will cuss the system you have written!

Whatever system you implement the use stored procedures should minimise
round trips and it should help you avoid SQL injection if you use strict
typing.

This is more to do with layout, putting fields in the logical order,
(possibly) give them templates or defaults, avoid excessive mouse
intervention, make sure that your form can be accessible by persons with
different abilities, make your process "intuative" and the workflow flows.
Make sure that information is logically grouped and you avoid information
overload and clutter.

Use of stored procedure should help this, use of templates so forms have a
common structure, use of meaningful comments and good documention.

John

LOL

Never present TWO designs to a user. You will walk out of the meeting 5
hours later with FIVE.

Other than that, John's advice is sound. <g>

-ralph

 

[John Bell]

LOL

Never present TWO designs to a user. You will walk out of the meeting 5
hours later with FIVE.

I can't believe I put that...

Other than that, John's advice is sound. <g>

That's nice to know!

-ralph

John