PortsideTechnologies.co.uk - Web Design - Episode 7

SITE 75% COMPLETE:

Modified the accounts page and database some what, mainly to include a VAT calculator, the tax can then be broken out and stored in the database.

• Added transaction type drop down list; this enables the user to select either debit or refund, on selection some code-beind determines the selected value and determines "r" for refund, "d" for debit which are the values that get strored.
• Changed the type of the transaction type column in the database from integer to a single character (for "r" or "d"). This table will also be used for credits so the transaction type for credits will be "c" imaginitively.
• I wanted to be able to rationalise credits, debits, and refunds in the table, so i added a further column called multiplier which is populated with "-1" for debits and "1" for refunds and credits, i can use this value later when displaying accounts in reports.
• Removed the VAT text box as VAT will now be calculated in the code-behind section.
• Added the VAT calculation which produces the following output:
  • Cost before VAT.
  • Cost after VAT.
  • Cost of VAT.
  • Total cost before VAT.
  • Total cost after VAT.
• Added the new columns to the accounting transactions table.

Completed adding controls, code-behind, and database table for the cases component type, the details of which follow:

• Added Ajax update panel to ther case tab panel to enable asynchronous postbacks.
• Added controls to case update panel for selection of case attributes.
• Added updateProgress Ajax control extender to case update panels, to indicate sql transactions.
• Added label to case tab panel to show status of sql transactions.
• Finalised case database table schema.
• Completed code-behind to write case tsb panel controls attributes to the case database table.
• Added updateProgress Ajax control extender to case update panel, to indicate sql transactions.
• Added label to expenditure tab panels to show status of sql transactions.

Added a column to all product tables and set the Computed Column Specification, this will automatically calculate the sale price from the price column multiplied by the markup percentage (which varies for different components). This means that the sale price does not have to be calculated in the code, reducing the need to modify code, instead you can just modify the formula in the Computed Column Specification in sql for each of the required tables.