scottf22 15 Newbie Poster

Sounds like you have everything you need to get the website running. I would take the HTML from dreamweaver web pages and paste it into asp.net web pages. You need ADO.Net to connect the database to the controls on the web page, this is depending on what you have in the DB of course. ADO.Net is built into ASP.Net so you don't need to go our and get anyting else. It is just a subset of database tools for interacting with the databse.

You can run Asp.Net from you computer to make sure the website is hooked to the database correctly and check out the web pages to see that they load properly in the browser.

You sound a bit overwhelmed at the moment. You need to break the task of "putting it all together" down in to small tasks that you need to do to get it out there.

My advice:
1) Spend more time with ASP.Net, create really simple web pages and understand how it works and see that it creates web pages in your browser

2) Move the HTML from Dreamweaver into ASP.Net web pages

3) Learn ADO.Net so you can to "talk" to your databae.

4) Learn how to debug your code and step through the code so you become familar with how it all hangs together.

5) When it all works on your machine, you need to move it to a hosted web server.

Step 5 is the last step and is were the …

scottf22 15 Newbie Poster

I don’t know exactly why this is happening but looking at your code I detect a code smell. I mean that in the nicest way possible .

What I would do is simplify your code by separating the formatting away from the calculations. Those are two separate tasks, or concerns, and so should be handled separately. This separating out of tasks so they are independent of each other is one of the tenets of the SOLID principles of program design. The “S” in SOLID stands for Separation of Concerns.

When you combine the two in one function (formatting and calculations) the code is more complicated and finding a solution to a bug is therefore more complicated. When finding a bug like this the programmer could ask themselves, “Is the problem coming from the formatting or is the calculation algorithm off or maybe I simple entered in the wrong data?” In other words there are too many possible ways this algorithm is breaking down. When you try to do more that one thing at a time it is very difficult to test the code to trace a bug.

Here is an example of what you can try so you can narrow down where things are going wrong:
I don’t know what the Function TRS does but here I am assuming it returns a double.

Public Class FindTotal

Public Function CalculateTotal(dblsharbal as Double, dblworkbal as Double, dblsalabal as Double, dblprofit as Double) as Double
    Dim total as double = dblSharbla …
ddanbe commented: Good answer. +15