Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
User's point of view
Message
From
13/12/2001 19:20:06
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Title:
User's point of view
Miscellaneous
Thread ID:
00594177
Message ID:
00594177
Views:
59
Hi
I want to find a good design for a parent-child form that doesn't use an edit mode (to me, most of times the edit mode only offers advantages to the programmer ).
For instance, I guess that if the user clicks the save button he would expect to save all the records from both tables ,but I'm not sure what he'd expect by clicking the revert button or the delete one. These are the some of the options I got in mind

For revert button:

last changed field
all records (both tables)
last changed record
last used table

For delete button:

Delete the record parent and therefore its child records
Delete the current record


which is the most recommendable solution for both buttons?

Another thing that concerns me is when user wants to search for a record or move to the another (parent records), should I save the current record automatically , not saving at all or give the user a chance to commit or revert changes? The problem with no saving is that when he decides to close the form he might run into different mistakes he left in the records and he will find himself in a confusing situation. Another issue is about desactivate the revert and save buttons, should I apply it or is not necessary and acceptable to leave these two buttons always enabled?


Thanks in advance
Next
Reply
Map
View

Click here to load this message in the networking platform