I am coding a proggy that once it is done will have nearly 60 forms all basically containing simple coding, nothing too major....will this be a bad program, or will the amount of forms not really hold a bearing.
I don't wan't it to run slow...I just need that many forms.
Any infor is greatly appreciated,
Darkcloud
I can't find any specific limit for the number of forms, but if there is one it's probably more than 60. There are several problems that I can see with that many forms.
- The "bookkeeping involved with remembering what each form is for
- If you need to open them all at once it will be slow
- If you need to have many of them loaded at the same time your program will require a lot of memory
- If you don't unload them properly you will have "memory leaks" and you may also find that the O/S thinks your program is still running even after "End"
What is it that causes you to need that many forms?
Well if you have that many forms and they are ALL needed then what you might want to consider to make it a "good" program is how you are going to navigate through so many forms.
A person who is using the program will not want to open and close 60 different forms to do things... they would sooner give up.
So you may want to consider making your forms MDI (Read up on this)...
OR
Rationalize your forms so they are "TABS" on the same form (Again read up on this)
OR
See if you can compact it such that more information is displayed on the same form that is relevant.
It is neccessary for my proggy to have that meny forms.
As one form is loaded the previous one is unloaded. Only one or two actually stay open. I haven't had any real issues play testing in VB5, but I ofcourse have not yet run a EXE yet. I was just curious. Oh yeah is there a code that I can use to ensure that all forms have been succesful unloaded.
I usually use:
Unload me
frmAnotherForm.Show
Is there a better way to unload forms...maybe a code that will ensure that once used that no forms are still loaded?
P.S Do you think that using the:
unload me
frmAnotherForm.Show
Is bad coding and will it, if used a lot, slow down my overall proggy?
(remember I allways close one before loading the next. Only the main form stays on till it is closed at the end of the session.)
You have me curious :D
I have to ask....
- What possible reason could you have for 60 forms?
- Are any of the forms "similar" to each other?
(ie same header and footer but with different questions)
Please feed me!!! ;)
My program is a Tutorial. It emulates various printing softwares. It lacks the actual Bi-Directional communication and scanning software, that the original software has. I am currently working for an outsource of a large and popular printer/scanner/fax/PC company you all have heard of, but I am not allowed to submit any names. I am a responsible for designing various hardware and software tutorials for training the companie's employees. I have recently hit big time when I informed my higher ups that I could design software that will emulate their original softwares and provide their Tech support agents with a powerful tool in the feild. Some of my software will emulate booting into Safe Mode and allow teadious manual uninstalls and various registry settings. The keyword here is EMULATES. At no time does my software actaully install, uninstall, reboot, or the like...it just allows the technician to basically follow a customer through those tasks. Ofcourse there is more to it than that but you get the giff. In the end I feel that nearly 60 forms are all neccessary as they are. If I add tab strips, combine forms and etc, I would be breaking the illusions. Laterz!
If you only have one or two form shown at the same time, you need only two forms, that loads all controls, visible/invisible them moves, resizes and whatever every tim you load them. That's more complicated but it's a way out.