about vb.net forms

madu

Hi im using vb.net 2003 version pls help me out to resolve the problem of creating forms to develop a desktop stock control system to a bookstore im planning to design a stock control system to a bookshop which is my final yr project of my degree can pls give me an idea of the forms that you have to create for a stock contol system

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Mikkel Meyer Andersen19y ago
Hi, It sounds like that you should use events; have you tried to see whether they can solve the problem? Another possibility is to incorporate the observer-pattern.
Mikkel Meyer Andersen19y ago
Hi, It sounds like that you should use events; have you tried to see whether they can solve the problem? Another possibility is to incorporate the observer-pattern.
Jarrod19y ago
What I would do is make your seperate forms and keep them strongly encapsulated. If a user is then verified do something like this (psuedo code).

On user button click
if ( verified == true )
    close out current form
    create the new form object
    new form.Run()
else "Sorry, you are not verified"

by having the forms know about each other and access to their properties (ie visible) you create an issue that will arise down the road where you want to change something on one form like its accessor methods and the app crashes... but by having the two forms seperated and having one just call the others Run method then you can change everything you need without the fear of issues because neither know anything about each other other than to tell one to run.
Jarrod19y ago
What I would do is make your seperate forms and keep them strongly encapsulated. If a user is then verified do something like this (psuedo code).

On user button click
if ( verified == true )
    close out current form
    create the new form object
    new form.Run()
else "Sorry, you are not verified"

by having the forms know about each other and access to their properties (ie visible) you create an issue that will arise down the road where you want to change something on one form like its accessor methods and the app crashes... but by having the two forms seperated and having one just call the others Run method then you can change everything you need without the fear of issues because neither know anything about each other other than to tell one to run.