Click here to Skip to main content
15,897,371 members

Comments by gregoryayca (Top 2 by date)

gregoryayca 3-Jan-14 12:23pm View    
I understand "PaintShopPro" is an painting application but remember that we are a talking about a very common scenario in the business industry. A typical file maintenance, Clients, Items, Vendors, Contacts, Employees, etc. When you go a bank to open a new account, they go first to a form where they search your name or S.S. # to verify if you have or had an account already even so if you say you don't have it. If they do not find you they click a button to create a new account and a new form is opened, in this new form they have all kind of validations for example they verify the address you provide against a valid address directory and tons of validation for other fields, when everything is Ok they press a confirm button to Create the account where the Account (Checking/Savings) number is assigned and the Database updated. If you decide to open savings account then they press a button to open a new form to Open a savings account with fields maybe different that the one for Checking and so on. Similar procedure repeats for Clients, Vendors, Employees etc. Do you think we can have all these in one form ? What about OOP, modular design is one of the benefits.
I imagine having everything in a large form hiding some fields and making appear others with tons of events and methods and making it more difficult to maintain. The app at the same will use a lot of machine resources.
Thanks
gregoryayca 3-Jan-14 11:27am View    
Look this comment that I have received. What do you think?
Why would you call some form a child? Child-parent relationship between forms is made defunct, unless you mean MDI parent/child, which I would never recommend to use.
I would strongly advise to do all application in only one form (not counting some modal forms, if you need any).
—SA