Microsoft Access or Stand alone Database Application with Dynamic Tables and Forms -- 2
Budget: $750 – $1,500 AUD
Microsoft Access or a stand alone Database Application with Dynamic Tables & Forms for a construction estimating service.
The application will calculate costs & percentages of all labour, material & plant hire required for building projects.
*************** CONDITIONS OF PROJECT ****************
-Completion Date - Friday 4th July, 2025
-Daily communication updates required from day 1 to completion date
-IP (Intellectual Property) agreement to be signed, dated & sent to me before starting project so that all work completed belongs to me.
-IF YOU CANNOT MEET ALL THE ABOVE CONDITIONS, DO NOT BID
**************************************************************
1.0 REFERENCE TABLE DESIGNS
I have created some sample 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 estimate work sheet
2.2 price file-1 (costing library)
2.3 price file-2 (unit rates/ factors from estimate 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 FUNCTIONS & FEATURE REQUIREMENTS
3.1 if Access is the build application, then must be able to run in both the 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 combination of; manually selecting items from the price file, selecting 1 or more recipes or copying a previous estimate.
3.3 the price file will have a 14 character code convention.
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 calculation routines that must auto-populate the “qty” field in the estimate sheet (detailed info supplied).
3.7 “hide” routines that will hide specific custom text from a print view (detailed info supplied).
3.8 all data fields from all tables & textboxes must be searchable.
3.9 there needs to be a “refresh” data function control button in the estimate worksheet that updates all tables with any changes to the price file.
3.10 there will need to be a “renumbering” data function in the price file so that I can easily add, edit or delete data & renumber the code conventions.
3.11 when adding price file or recipe items into the estimate worksheet, all data must be displayed in its numeric sequence order.
3.12 startup window user login, pwd & company selection to open the application.
3.13 there will need to be a function in the estimate sheet that the user can select 1 or more line items to not be printable in any report, internal or external but visible to the user only.
3.14 default application font style & size to be confirmed.
3.15 any repetitive data entries in forms or textboxes should have a drop-down menu box to select from a list of most common options available instead of having to manually enter data each time.
3.16 there needs to be a qty & value rounding function in the estimate 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 estimate sheet to another, or drag & drop data.
3.18 you need to be able to have multiple estimate sheets opened at the same time.
3.19 you need to be able to have opened side by side & work in 2 estimate work sheets.
3.20 tables & forms tool bars with tool tips as required.
3.21 the application must not allow a price file item “description or rate” once added into the estimate worksheet to be editable. The application must warn & give the user the option to create a “custom item” with the same data, but with a specific code convention for “custom items”.
3.22 the application must save & store “system” & “jobs” database folders & files with all application data.
There will need to be a "backup" folder within the application that allows automatically saves all data when closing the application each time.
3.23 application version must be displayed on all main windows.
3.24 application must auto generate job/ client numbers for all new jobs but have a cancel or delete job function also.
3.25 application must display job numbers to allow for revisions, for example client/ job number 1050-1 is the first estimate, but if changes are made or additional estimates are required the next estimate would be 1050-2, 1050-3 & so on.
3.26 the estimate worksheet must have a “reprice” function so that all data in the open estimate sheet is updated with the current price file data.
3.27 the application must be able to search for any data in any estimate sheet, wether its an estimate sheet currently being worked on or a previously completed estimate sheet. Part of the search must not only be price file items, but also any manual entry text from any textbox in the application.
3.28 status & alerts column to be shown in the estimate sheet which meet specific criteria/ rules.
3.29 the application should warn the user of any items that have been doubled up in the estimate sheet & give an option to combine the qty (quantities) of the item instead of showing multiple line items.
3.30 all recipes added into the estimate sheet must be shown at the beginning of the estimate as a record to the user of the recipe & the qty of the recipe, for example +1, +2 or even a negative for example -1 (which would cancel a recipe that was mistakenly added to the estimate sheet).
3.31 application 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 options will be multiple estimate comparisons, price file report, recipes list report, estimate 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 printing not viewing.
3.33 line items in the estimate sheet must have a right hand mouse click menu with options to either “substitute” the existing 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 existing line item must retain all its data including any manual entries.
3.34 when opening the price file while in the estimate sheet, the default search must be the live “group” but give an option to also search “all groups”.
3.35 when clicking or selecting any cell or line item in any table or textbox within the application, the entire data line must be hilited.
3.36 when adding new items into the estimate 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 estimate sheet, all their line items should show in blue font until 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 entire line item font to red, until its updated to “completed” which should then change & remain black.
3.39 although all price file items will have their own unique code, they must have the ability to be added into any group within the estimate sheet, not just their own price file group.
3.40 there must be an "email" feature in the reports form to email any reports to clients.
3.41 application manual required to use of the application.
The application will calculate costs & percentages of all labour, material & plant hire required for building projects.
*************** CONDITIONS OF PROJECT ****************
-Completion Date - Friday 4th July, 2025
-Daily communication updates required from day 1 to completion date
-IP (Intellectual Property) agreement to be signed, dated & sent to me before starting project so that all work completed belongs to me.
-IF YOU CANNOT MEET ALL THE ABOVE CONDITIONS, DO NOT BID
**************************************************************
1.0 REFERENCE TABLE DESIGNS
I have created some sample 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 estimate work sheet
2.2 price file-1 (costing library)
2.3 price file-2 (unit rates/ factors from estimate 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 FUNCTIONS & FEATURE REQUIREMENTS
3.1 if Access is the build application, then must be able to run in both the 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 combination of; manually selecting items from the price file, selecting 1 or more recipes or copying a previous estimate.
3.3 the price file will have a 14 character code convention.
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 calculation routines that must auto-populate the “qty” field in the estimate sheet (detailed info supplied).
3.7 “hide” routines that will hide specific custom text from a print view (detailed info supplied).
3.8 all data fields from all tables & textboxes must be searchable.
3.9 there needs to be a “refresh” data function control button in the estimate worksheet that updates all tables with any changes to the price file.
3.10 there will need to be a “renumbering” data function in the price file so that I can easily add, edit or delete data & renumber the code conventions.
3.11 when adding price file or recipe items into the estimate worksheet, all data must be displayed in its numeric sequence order.
3.12 startup window user login, pwd & company selection to open the application.
3.13 there will need to be a function in the estimate sheet that the user can select 1 or more line items to not be printable in any report, internal or external but visible to the user only.
3.14 default application font style & size to be confirmed.
3.15 any repetitive data entries in forms or textboxes should have a drop-down menu box to select from a list of most common options available instead of having to manually enter data each time.
3.16 there needs to be a qty & value rounding function in the estimate 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 estimate sheet to another, or drag & drop data.
3.18 you need to be able to have multiple estimate sheets opened at the same time.
3.19 you need to be able to have opened side by side & work in 2 estimate work sheets.
3.20 tables & forms tool bars with tool tips as required.
3.21 the application must not allow a price file item “description or rate” once added into the estimate worksheet to be editable. The application must warn & give the user the option to create a “custom item” with the same data, but with a specific code convention for “custom items”.
3.22 the application must save & store “system” & “jobs” database folders & files with all application data.
There will need to be a "backup" folder within the application that allows automatically saves all data when closing the application each time.
3.23 application version must be displayed on all main windows.
3.24 application must auto generate job/ client numbers for all new jobs but have a cancel or delete job function also.
3.25 application must display job numbers to allow for revisions, for example client/ job number 1050-1 is the first estimate, but if changes are made or additional estimates are required the next estimate would be 1050-2, 1050-3 & so on.
3.26 the estimate worksheet must have a “reprice” function so that all data in the open estimate sheet is updated with the current price file data.
3.27 the application must be able to search for any data in any estimate sheet, wether its an estimate sheet currently being worked on or a previously completed estimate sheet. Part of the search must not only be price file items, but also any manual entry text from any textbox in the application.
3.28 status & alerts column to be shown in the estimate sheet which meet specific criteria/ rules.
3.29 the application should warn the user of any items that have been doubled up in the estimate sheet & give an option to combine the qty (quantities) of the item instead of showing multiple line items.
3.30 all recipes added into the estimate sheet must be shown at the beginning of the estimate as a record to the user of the recipe & the qty of the recipe, for example +1, +2 or even a negative for example -1 (which would cancel a recipe that was mistakenly added to the estimate sheet).
3.31 application 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 options will be multiple estimate comparisons, price file report, recipes list report, estimate 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 printing not viewing.
3.33 line items in the estimate sheet must have a right hand mouse click menu with options to either “substitute” the existing 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 existing line item must retain all its data including any manual entries.
3.34 when opening the price file while in the estimate sheet, the default search must be the live “group” but give an option to also search “all groups”.
3.35 when clicking or selecting any cell or line item in any table or textbox within the application, the entire data line must be hilited.
3.36 when adding new items into the estimate 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 estimate sheet, all their line items should show in blue font until 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 entire line item font to red, until its updated to “completed” which should then change & remain black.
3.39 although all price file items will have their own unique code, they must have the ability to be added into any group within the estimate sheet, not just their own price file group.
3.40 there must be an "email" feature in the reports form to email any reports to clients.
3.41 application manual required to use of the application.