This seems to be a question a 2 year old might ask, but for a lack of knowing where to look for these answers, I am asking it here.
This pertains to VB .Net 2005 Express Edition. This is a Windows Form Application.
I am working on a program. This program will access a database occasionally, write/read to files, contain multiple forms but doesn't have a Multiple Document Interface, and do several other things that would be a seperate category of thought altogether. When the program starts, I need to check a settings file. If it exists and has data, I will load my Primary form where most of the program tasks are performed; otherwise, I will need to display a Settings form to get this data from the user.
How do I organize my solution? Where should the above logic go in the code? How do I provide a common sense structure to my project so that Database functionality is contained in an object or group of objects seperate from the business code and the interface code?
I know this is a mouthful and not all that clear cut. Any help you experts can provide would be invaluable. I would rather rebuild my program now than to have it become some sort of hideous progeny that controls me.