Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Breaking up a Large Project
- Thread starter bgirard
- Start date
Well, the normal way to do your project is to get your design right. It seems that you started off building a prototype.
The best way is to convert the existing application into modules - into separate entities. I am not sure if you know about Object Oriented Programming. Merely converting a couple of files into a DLL might not be a good idea. You might want to look at your current application long and hard and find out the various links and relations between different forms.
Once you know that, you can use OOP design methodology to rehash your application. This might take some of your time but in the long run you surely would have a better control and maintenance would be much much easier. You will be able to plug in and unplug object modules at will.
You may ask me if you have any more questions.
The best way is to convert the existing application into modules - into separate entities. I am not sure if you know about Object Oriented Programming. Merely converting a couple of files into a DLL might not be a good idea. You might want to look at your current application long and hard and find out the various links and relations between different forms.
Once you know that, you can use OOP design methodology to rehash your application. This might take some of your time but in the long run you surely would have a better control and maintenance would be much much easier. You will be able to plug in and unplug object modules at will.
You may ask me if you have any more questions.
- Thread starter
- #3
I appreciate your response.
You are corect in the fact that this project did start out as a prototype and is getting too large.
I am aware of OOP but haven't used this technique as of yet.
There really aren't any distinctive links between the majority of the forms as each form accomplished specific tasks (ie customer, vendors, Quality Control).
I thought of having one 'main' form and having it call seperate .exe's for each of the specific tasks. I realize this isn't the best solution however it might be an interim one.
What books and/or web tutorials would you recommend to learn OOP in VB ??
You are corect in the fact that this project did start out as a prototype and is getting too large.
I am aware of OOP but haven't used this technique as of yet.
There really aren't any distinctive links between the majority of the forms as each form accomplished specific tasks (ie customer, vendors, Quality Control).
I thought of having one 'main' form and having it call seperate .exe's for each of the specific tasks. I realize this isn't the best solution however it might be an interim one.
What books and/or web tutorials would you recommend to learn OOP in VB ??
Yes the method of calling separate exes would work in a short term. You may check out "Doing Objects in Microsoft Visual Basic 6" by Deborah Kurata. I found it to be good and informative.
Try it out and I am sure it will help you a lot.
Let me know if you have any questions.
Try it out and I am sure it will help you a lot.
Let me know if you have any questions.
- Status
