Put the daily task in the programming scope.
A useful engagement names the screen, its underlying logic and the evidence that lets your team accept the change.
Improve the form people actually use
Identify the entry screen, required fields, validation messages and actions included in the milestone. Show the existing task with representative records and specify how the revised form should handle corrections, empty values and a record another user is editing.
Receive reports with a defined record basis
State the filters, date interpretation, grouping and rounding used by each report. Supply a small expected result with the source records behind it. Include printing, export formatting and access to sensitive fields when those outputs form part of the engagement.
Keep link changes attached to a release
A working frontend can still point at the wrong file or a source with different fields. Name the frontend edition, source location and required tables in the delivery record. Receive table-level checks and business-workflow results before distributing the revised application.
Make the application and its data source agree.
The AL76 workspace demonstrates a link-change acceptance task. Inspect the staging exception, validate a matching source and receive the exact frontend and target accepted by the release owner.
Exercise the link plan before accepting the change.
AL76 makes three linked tables and one missing field visible in a complete receiving sequence.
Run the AL76 receiving exercise
Validate the unavailable legacy share to hold three links. Select staging and inspect the Orders row: Total is present, but the application requires Amount. Choose the matching live share, validate again and switch to Release owner. Record the two acceptance cases, accept the release and export its receipt.
Open the link acceptance demoIdentify the frontend and shared data separately
Microsoft describes a split Access database as a shared backend containing tables and a frontend containing the other application objects. Use that distinction to inventory the files, compatible versions and user copies included in your programming request.
Primary reference: Microsoft split database structureSpecify the evidence for a changed link
Microsoft documents refresh and relink operations through Linked Table Manager, with a status for each affected table. Include source availability, field names and the forms or reports consuming those tables in your acceptance cases. Agree the appropriate procedure for your Access version.
Primary reference: Microsoft linked-table managementScope a wider database application separately
If your request includes a new record service, substantial import processing or a replacement application, define those deliverables alongside the Access work. Preserve clear ownership of the desktop frontend, data service and deployment environment.
Discuss a related database application projectCommission a change your team can receive.
Bring one business operation and its actual environment into the quotation.
Identify the editable application
List the frontend and backend files, Access and Windows versions, Office bitness, references and installed components. Confirm that you control the editable source and can provide an approved working copy. Describe who uses each copy and where the operational data resides.
Specify the programming milestone
Name the forms, saved queries, reports, macros and VBA modules affected by the request. Attach the current behavior and expected outcome for each action. Separate a targeted enhancement from file repair, data cleanup, a backend change or a full replacement.
Reproduce the task with representative data
Agree an anonymised dataset and reproducible steps. Include a normal record, an incomplete entry, a failed connection and any calculation boundary relevant to the task. Establish the current output before changing the application logic.
Develop against the receiving contract
Keep table and field expectations visible while changing code or connections. Record report totals and the behavior of validation, edits and exports. For a changed source, verify each affected table and the application objects that consume it.
Approve a controlled application release
Agree the backup and restoration check, the user test cases and the person who approves distribution. Confirm how users receive the frontend and how obsolete copies are retired. Include shared-file permissions and the response to an unavailable backend.
Hand over the maintainable source
Receive the editable application, module changes, query and report definitions, dependency inventory and release instructions. Record the accepted source configuration and rollback method. Set the support contact, defect handling and process for quoting later enhancements.
Application and environment inputs
- Provide the current file types and identify the editable source separately from any distributed compiled frontend. Include a dependency list, external references, drivers and the versions installed on representative user PCs.
- Describe the data-entry journey and reporting output in business terms. Mark the objects that need new logic, the records they read or write and the fields that require validation or restricted visibility.
- List every linked source and its technical owner. Agree how approved connection details will be supplied through the project channel, with file access, authentication and licensing responsibilities assigned.
- State concurrent users, record volumes, remote-working requirements and existing file locations. Discuss environment suitability before assuming that the current sharing arrangement can support a new use pattern.
Acceptance, distribution and ongoing care
- AL76 expects Customers(CustomerID, Name), Orders(OrderID, CustomerID, Amount) and OrderLines(LineID, OrderID, Qty). The staging Orders definition contains Total instead of Amount, so its link plan holds that table.
- The matching source contains two Customers, three Orders and four OrderLines in the exercise. Record counts support reconciliation; agree additional value, relationship and business-total checks for your actual dataset.
- Include input validation, missing files, denied permissions, incompatible references, concurrent edits and report/export checks where they affect the commissioned change. Assign the person who accepts each case.
- Ask for discovery, programming, data preparation, environment work, deployment and maintenance to be estimated with clear boundaries. Confirm milestones, third-party licence costs, support hours and how changed requirements affect the quote.
Receive the frontend, its bindings and the acceptance record.
AL76 supplies a compact link-change model to attach to your programming enquiry.
| Record | Example inputs | Required output and control |
|---|---|---|
| Frontend release | Dispatch.accde / release 12 | Identify the distributed build and retain the editable source for the engagement. |
| Target source | Legacy, staging or live Ops_be.accdb | Record the approved location separately from the current application draft. |
| Table contract | Customers, Orders and OrderLines / named required fields | Hold a binding when the source is unavailable or a required field is missing. |
| Validation result | Staging 2 ready / 1 held; matching source 3 ready / 0 held | Revalidate after the selected target changes. |
| Release acceptance | Release owner / backup and order-workflow cases | Receive the current link plan only after its named acceptance cases. |
| Receiving receipt | AL76-R01 / frontend 12 / validation revision / target and counts | Retain accepted values when the next draft selects another source. |
The unavailable legacy share holds all three links. Staging supplies the expected Customers and OrderLines fields, but Orders lacks Amount, leaving two ready bindings and one hold. The matching live source satisfies all three definitions with row counts of 2, 3 and 4. The Developer can validate; the Release owner records the backup and order-workflow acceptance cases before receiving AL76-R01. A later source change clears current validation while the exported receipt retains the earlier target and counts.
Request quotations against the same application milestone.
Send providers the same file inventory, affected objects, anonymised task and receiving cases.
| Option | Published focus | Ask in your demo |
|---|---|---|
| eSoftware Associates | Describes Access development, Office and SQL hybrid arrangements, migration and continuing support. | Which frontend, source bindings and workflow checks will be included in the accepted milestone? |
| Phoenix Consultants Group | Describes database repair, programming, structure assessment, migration and support engagements. | How will affected table definitions, application objects and receiving evidence be recorded for our change? |
| Dan’s Consulting | Offers Access design/build, forms, reports, VBA enhancements, repair and conversion work. | What editable source, user-copy distribution instructions and accepted release record will we receive? |
Agree whether the quotation covers a specific form or report change, a broader application enhancement or a backend move. AL76 adds a repeatable receiving exercise with an explicit field mismatch and a retained release receipt.
Category reference: Microsoft documentation: managing linked tables. Use the documentation for the Access version and source type specified in your engagement.
Connect desktop programming to your wider application.
Discuss the Access frontend alongside data-service, migration and operating requirements when they belong in the same project.
Explore marketplace development servicesArrange your Access programming engagement
Settle the files, task and receiving responsibility before allocating the work.
What should we send for a programming quotation?
Describe the operation that needs to change and provide the application version, file inventory and affected forms, queries, reports or VBA modules. Include an anonymised example, current output and expected result. Identify the editable-source owner and the person who will accept the release.
Can we commission a single form or report change?
Yes. Define the exact object, the records it uses and the receiving cases for that milestone. Include dependent queries, calculations, exports and any user permissions affected by the change. Codeblix can scope the programming work against that boundary.
How is a linked-source change included in the project?
Name the existing and intended source, affected tables, required fields and Access version. Agree connection and permission checks in an approved environment, followed by tests of the forms and reports that use those tables. Retain the accepted frontend and target configuration in the release record.
What does the link acceptance demo exercise?
AL76 is a browser-based receiving exercise for your project brief. Select sources, inspect required fields and record an owner-approved release receipt. Use its missing-source and missing-field cases to define the work and acceptance evidence for your Access application.
Which files and dependencies should the engagement cover?
Include editable source, distributed frontend files, backend locations, external references, required drivers and representative PC configurations. Confirm Access version, Office bitness, component licensing and who supplies authorized environment access.
Can an Access project include a SQL Server connection?
Include the proposed database, supported driver, authentication method, table ownership and affected queries in the request. Scope compatibility, field mapping, write behavior, reconciliation and rollback after the environment is assessed. Confirm the frontend and server responsibilities separately.
How are delivery time and programming cost agreed?
Request a written estimate for the specified application milestone, representative data and acceptance cases. Separate discovery, development, data cleanup, environment changes and release work. Confirm scheduling, third-party charges and how additional objects or requirements are priced.
What should we receive at handover?
Specify editable application source, changed modules and queries, report definitions, dependencies, configuration instructions and the accepted release record. Include frontend distribution, backup restoration, rollback, support contacts and the agreed terms for future maintenance.