Microsoft Access or Stand alone Database Application with Dynamic Tables and Forms For a Building Estimation Service
Budget: $250 – $650 AUD
Microsoft Access or stand alone Database Applica on with Dynamic Tables & Forms for a building estima on service.
The application will calculate costs & percentages of all labour, material & plant hire required for building projects.
1.0 Reference Table Designs
I have created some reference table designs you need to follow & code to my requirements;
1.1 main estimate work sheet
1.2 price file
1.3 recipes
1.4 reports
2.0 Main Table Designs & Coding
2.1 esmate work sheet
2.2 pricing by price file
2.3 pricing by unit rates/ factors (from esmate sheet historical data)
2.4 recipes
2.5 reports for internal & external use
2.6 application must also include a quote, invoice & receipt feature with my business logo
3.0 Other Info & Features
3.1 if Access application must be able to run in current version of windows & office, but also previous version.
3.2 a new estimate worksheet by default will always be blank, and data can be added by a combina on of; manually
selecting items from the price file, selecting 1 or more recipes or copying a previous estimate.
3.3 (14) character code conventions
3.4 search forms on all tables & forms throughout the application
3.5 sort function where data in any tables can be sorted/ filtered by a specific table field label
3.6 calcula on rou nes that will auto-populate the “qty” field in the esmate sheet (detailed info supplied)
3.7 “hide” rou nes that will hide specific custom text from a print view (detailed info supplied)
3.8 all data fields from tables & textboxes must be searchable
3.9 there needs to be a “refresh” data func on control bu on in the esmate worksheet that updates all tables with
any changes to the price file
3.10 there will need to be a “renumbering” data func on in the price file so that I can easily add, edit or delete data
& renumber the code conven ons
3.11 when adding price file or recipe items into the esmate worksheet, all data must be displayed in numeric
sequence order
3.12 startup window user login, pwd & company selec on to open the applica on
3.13 there will need to be a func on in the esmate sheet that the user can select 1 or more line items to not be
printable in any report, internal or external
3.14 default applica on font style & size to be confirmed
3.15 any repe ve data entries in forms or textboxes should have a drop-down menu box to select from a list of most
common op ons available instead of having to manually enter data each me
3.16 there needs to be a qty & value rounding func on in the esmate sheet that can either round up or down by a
specific value
3.17 you need to be able to copy & paste any data from 1 esmate sheet to another, or drag & drop data
3.18 you need to be able to have mul ple esmate sheets opened at the same me
3.19 you need to be able to have opened side by side & work in 2 esmate work sheets
3.20 tables & forms tool bars with tool ps as required
3.21 the applica on must not allow a price file item “descrip on or rate” once added into the esmate worksheet to
be editable. The applica on must warn & give the user the op on to create a “custom item” with the same data, but
with a specific code conven on for “custom items”.
3.22 the applica on must save & store “system” & “jobs” database folders with all applica on data
3.23 applica on version must be displayed on all main windows
3.24 applica on must auto generate job/ client numbers for all new jobs
3.25 applica on must display job numbers to allow for revisions, for example client/ job number 1050-1 is the first
esmate, but if changes are made or addi onal esmates are required the next esmate would be 1050-2, 1050-3 &
so on.
3.26 the esmate worksheet must have a “reprice” func on so that all data in the open esmate sheet is updated
with the current price file data
3.27 the applica on must be able to search for any data in any esmate sheet, wether its an esmate sheet currently
being worked on or a previously completed esmate sheet. Part of the search must not only be price file items, but
also any manual entry text from any textbox in the applica on
3.28 status & alerts column to be shown in the esmate sheet which meet specific criteria
3.29 the applica on should warn the user of any items that have been doubled up in the esmate sheet & give an
op on to combine the qty (quan es) of the item instead of showing mul ple line items
3.30 all recipes added into the esmate sheet must be shown at the beginning of the esmate as a record to the user
of the recipe & the qty of the recipe, for example +1, +2 or even a nega ve for example -1 (which would cancel a
recipe that was mistakenly added to the esmate sheet)
3.31 applica on must be able to store & allow user to select pricing either from the price file or the “unit rates/
factors” library
3.32 part of the reports op ons will be mul ple esmate comparisons, price file report, recipes list report, esmate
status & alerts report. The reports must all have the ability to show or hide any of the fields related to the selected
report just from prin ng not viewing.
3.33 line items in the esmate sheet must have a right hand mouse click menu with op ons to either“subs tute” the
exis ng line item with another line item from the price file or open & search the price file or just delete the line item.
When this is selected the exis ng line item must retain all its data including any manual entries.
3.34 when opening the price file while in the esmate sheet, the default search must be the live “group” but give an
op on to also search “all groups”.
3.35 when clicking or selec ng any cell or line item in any table or textbox within the applica on, the en re data line
must be hilited.
3.36 when adding new items into the esmate sheet from the price file the default qty should be set to “0” & font
colour to red. Once the qty has been edited the font colour should change & remain black unless it meets one of the
“status” criteria or rules.
3.37 when recipes are added into the esmate sheet, all their line items should show in blue font un l the user edits
any of the fields which should then change the font colour back into black, unless it meets one of the “status” criteria
or rules.
3.38 any “status” other than “completed” should change the en re line item font to red, un l its updated to
“completed” which should then change & remain black.
The application will calculate costs & percentages of all labour, material & plant hire required for building projects.
1.0 Reference Table Designs
I have created some reference table designs you need to follow & code to my requirements;
1.1 main estimate work sheet
1.2 price file
1.3 recipes
1.4 reports
2.0 Main Table Designs & Coding
2.1 esmate work sheet
2.2 pricing by price file
2.3 pricing by unit rates/ factors (from esmate sheet historical data)
2.4 recipes
2.5 reports for internal & external use
2.6 application must also include a quote, invoice & receipt feature with my business logo
3.0 Other Info & Features
3.1 if Access application must be able to run in current version of windows & office, but also previous version.
3.2 a new estimate worksheet by default will always be blank, and data can be added by a combina on of; manually
selecting items from the price file, selecting 1 or more recipes or copying a previous estimate.
3.3 (14) character code conventions
3.4 search forms on all tables & forms throughout the application
3.5 sort function where data in any tables can be sorted/ filtered by a specific table field label
3.6 calcula on rou nes that will auto-populate the “qty” field in the esmate sheet (detailed info supplied)
3.7 “hide” rou nes that will hide specific custom text from a print view (detailed info supplied)
3.8 all data fields from tables & textboxes must be searchable
3.9 there needs to be a “refresh” data func on control bu on in the esmate worksheet that updates all tables with
any changes to the price file
3.10 there will need to be a “renumbering” data func on in the price file so that I can easily add, edit or delete data
& renumber the code conven ons
3.11 when adding price file or recipe items into the esmate worksheet, all data must be displayed in numeric
sequence order
3.12 startup window user login, pwd & company selec on to open the applica on
3.13 there will need to be a func on in the esmate sheet that the user can select 1 or more line items to not be
printable in any report, internal or external
3.14 default applica on font style & size to be confirmed
3.15 any repe ve data entries in forms or textboxes should have a drop-down menu box to select from a list of most
common op ons available instead of having to manually enter data each me
3.16 there needs to be a qty & value rounding func on in the esmate sheet that can either round up or down by a
specific value
3.17 you need to be able to copy & paste any data from 1 esmate sheet to another, or drag & drop data
3.18 you need to be able to have mul ple esmate sheets opened at the same me
3.19 you need to be able to have opened side by side & work in 2 esmate work sheets
3.20 tables & forms tool bars with tool ps as required
3.21 the applica on must not allow a price file item “descrip on or rate” once added into the esmate worksheet to
be editable. The applica on must warn & give the user the op on to create a “custom item” with the same data, but
with a specific code conven on for “custom items”.
3.22 the applica on must save & store “system” & “jobs” database folders with all applica on data
3.23 applica on version must be displayed on all main windows
3.24 applica on must auto generate job/ client numbers for all new jobs
3.25 applica on must display job numbers to allow for revisions, for example client/ job number 1050-1 is the first
esmate, but if changes are made or addi onal esmates are required the next esmate would be 1050-2, 1050-3 &
so on.
3.26 the esmate worksheet must have a “reprice” func on so that all data in the open esmate sheet is updated
with the current price file data
3.27 the applica on must be able to search for any data in any esmate sheet, wether its an esmate sheet currently
being worked on or a previously completed esmate sheet. Part of the search must not only be price file items, but
also any manual entry text from any textbox in the applica on
3.28 status & alerts column to be shown in the esmate sheet which meet specific criteria
3.29 the applica on should warn the user of any items that have been doubled up in the esmate sheet & give an
op on to combine the qty (quan es) of the item instead of showing mul ple line items
3.30 all recipes added into the esmate sheet must be shown at the beginning of the esmate as a record to the user
of the recipe & the qty of the recipe, for example +1, +2 or even a nega ve for example -1 (which would cancel a
recipe that was mistakenly added to the esmate sheet)
3.31 applica on must be able to store & allow user to select pricing either from the price file or the “unit rates/
factors” library
3.32 part of the reports op ons will be mul ple esmate comparisons, price file report, recipes list report, esmate
status & alerts report. The reports must all have the ability to show or hide any of the fields related to the selected
report just from prin ng not viewing.
3.33 line items in the esmate sheet must have a right hand mouse click menu with op ons to either“subs tute” the
exis ng line item with another line item from the price file or open & search the price file or just delete the line item.
When this is selected the exis ng line item must retain all its data including any manual entries.
3.34 when opening the price file while in the esmate sheet, the default search must be the live “group” but give an
op on to also search “all groups”.
3.35 when clicking or selec ng any cell or line item in any table or textbox within the applica on, the en re data line
must be hilited.
3.36 when adding new items into the esmate sheet from the price file the default qty should be set to “0” & font
colour to red. Once the qty has been edited the font colour should change & remain black unless it meets one of the
“status” criteria or rules.
3.37 when recipes are added into the esmate sheet, all their line items should show in blue font un l the user edits
any of the fields which should then change the font colour back into black, unless it meets one of the “status” criteria
or rules.
3.38 any “status” other than “completed” should change the en re line item font to red, un l its updated to
“completed” which should then change & remain black.