EDN Admin
Well-known member
Im very new to VB and programming in general, having previously only written a few macros using VBA in Excel and then built a simple application from a "teach yourself" book on VB2008 so if you can go easy on my lack of knowledge that would be most appreciated!
Having said that, Im probably jumping in too deep with my proposed application!
I am trying to build an application that will effectively do the job of 3 Excel spreadsheet calculations to make them more user-friendly, more professional looking and more robust, as well as allowing data from each calculation to transfer between the others
more easily. The calculations relate to design of acoustics in buildings, namely:
1. Noise from traffic etc outside through the building facade to inside rooms of the building;
2. The amount of "echo" within a room; and
3. Sound transfer between rooms through walls/floors.
I have been able to set up forms for each calculation referencing back to Arrays to look up information relating to losses through different types of constructions, etc and then taking the selected construction/sizes, etc and putting them into variables,
which are then looked at to fill text boxed on the form with a relatively complex calculation using logs etc automatically updating depending on the filled text boxed.
I anticipated the application being an MDI type. Using the toolstrip or menu bar a user could then add a new calculation of one of the three types. This would then call up a new version of the relevant form as a child within the MDI parent which
the user would be prompted to "name". The MDI Parent would have a tree-view to the left hand side, where each time a new form is loaded then the name is added to the list ("Office 1 - Facade Insulation", "Office 2 - Partition Sound Insulation", etc).
The problems I am facing and need help with are:
1. Is it going to be simpler to put the information into a database rather than creating multiple versions of each form which wouldnt be able to be disposed as the information in them would need to stay live so they could be recalled? I havent had
any experience using a database as yet, so had hoped I could do without it, but the more I get into this the more I think Im going to have to bite the bullet and learn how to use them.
2. If I do have to use a database, what would be the easiest one for a relatively simple application such as this? The database would have to be "project" specific such that when a new project is created a new database is created, and when a user saves
and then closes a project that database is saved and closed, and then a new database created when the user then selects File > New from the menu, etc.
3. I will need to be able to save the calculations to a project specific directory and then open or create a new unrelated project as each file would be for a different site; if you imagine one project may be in London and another in Manchester, therefore
the calculations associated with one site need to be in a different file to any other. How can I package up all the information for one site into a "saved file". Unfortunately the "teach yourself" guide simply shows how to save a .txt file; how
do you decide what file type you need to use and how do you package everything (e.g. either the information in all of the forms or the background database) into a single file that can then be opened when needed via the application?
Finally if it may help the application would be run on individual computers, does not need to connect via the web, etc, and dont need to worry about multiple people having a saved file open at the same time.
Many thanks for any help in advance.
View the full article
Having said that, Im probably jumping in too deep with my proposed application!
I am trying to build an application that will effectively do the job of 3 Excel spreadsheet calculations to make them more user-friendly, more professional looking and more robust, as well as allowing data from each calculation to transfer between the others
more easily. The calculations relate to design of acoustics in buildings, namely:
1. Noise from traffic etc outside through the building facade to inside rooms of the building;
2. The amount of "echo" within a room; and
3. Sound transfer between rooms through walls/floors.
I have been able to set up forms for each calculation referencing back to Arrays to look up information relating to losses through different types of constructions, etc and then taking the selected construction/sizes, etc and putting them into variables,
which are then looked at to fill text boxed on the form with a relatively complex calculation using logs etc automatically updating depending on the filled text boxed.
I anticipated the application being an MDI type. Using the toolstrip or menu bar a user could then add a new calculation of one of the three types. This would then call up a new version of the relevant form as a child within the MDI parent which
the user would be prompted to "name". The MDI Parent would have a tree-view to the left hand side, where each time a new form is loaded then the name is added to the list ("Office 1 - Facade Insulation", "Office 2 - Partition Sound Insulation", etc).
The problems I am facing and need help with are:
1. Is it going to be simpler to put the information into a database rather than creating multiple versions of each form which wouldnt be able to be disposed as the information in them would need to stay live so they could be recalled? I havent had
any experience using a database as yet, so had hoped I could do without it, but the more I get into this the more I think Im going to have to bite the bullet and learn how to use them.
2. If I do have to use a database, what would be the easiest one for a relatively simple application such as this? The database would have to be "project" specific such that when a new project is created a new database is created, and when a user saves
and then closes a project that database is saved and closed, and then a new database created when the user then selects File > New from the menu, etc.
3. I will need to be able to save the calculations to a project specific directory and then open or create a new unrelated project as each file would be for a different site; if you imagine one project may be in London and another in Manchester, therefore
the calculations associated with one site need to be in a different file to any other. How can I package up all the information for one site into a "saved file". Unfortunately the "teach yourself" guide simply shows how to save a .txt file; how
do you decide what file type you need to use and how do you package everything (e.g. either the information in all of the forms or the background database) into a single file that can then be opened when needed via the application?
Finally if it may help the application would be run on individual computers, does not need to connect via the web, etc, and dont need to worry about multiple people having a saved file open at the same time.
Many thanks for any help in advance.
View the full article