Design question -- dialogs for database input?

I have a relatively easy design question, but I'd like to hear some comments.  I've got an Access database with 3 tables that I display in a single view.  Up to this point everything has been read only -- there has been no ability to modify or add records.

Most of the items are displayed as edit boxes, but there are also radio buttons, check boxes and a clistctrl.  

My question is:  should I allow users to add/edit right from this screen, or should I create a separate dialog box for input?  I need to validate that they choose a unique # for the new record.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vinayak KumbarSr Program ManagerCommented:

In my view It is better to create the different dialog(s) for input(s) as u may have to do the validation for each field. If it is in the same dialog, the whole concept looks like clumsy(complex) and to handle it is also difficult. If U have different dialogs(I mean different classes!!!), then U can individually handle them. And the programming is also easy and clean.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
U have two alternative here
choose any one of them depending on the target user Since no design can be wrong any approach U choose will be OK as long as U make it simple and clean
It often makes sense to have related fields all displayed and changable in a single dialog.  Much better a little crowding then letting users get annoyed with having to pop up 18 different screens.
It is pretty easy to keep data validation code seperate from GUI Code.

A 'method' that I usually employ is to use the GUI DoDataExchange functionality, which 'knows' whether the data is being displayed, or validated.

In this way, on a validate, the DoDataExchange function is simply a screen scrapper, which populates some Data object, then asks it to validate itself.

This is a very simple solution, which is why I like it so much !!

>>I need to validate that they choose a unique # for the new record.

Shouldn't you be generating this for the user.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Programming

From novice to tech pro — start learning today.