Yes. NDAs are standard before production database access.

Yes when requirements are documented and stable.

Hire an advisor when you are unsure what to fix — platform choice, migration timing, budget justification, or whether the database is worth saving at all. Developers execute; advisors diagnose and prioritize. AccessDeveloper advisors often start with a one- to two-hour assessment, then hand off to our development team only if build work is the right next step — not before.

Yes, if your ACCDB or MDB file supports payroll, billing, or inventory and nobody documented how it works. An MS Access advisor maps dependencies, flags broken references and security gaps, and recommends whether to upgrade in-place, split the database, or migrate to SQL Server. Skipping this step is how US businesses lose data during rushed Office upgrades.

Signs a rebuild makes sense: recurring corruption, no primary keys, tables over 500,000 rows in a single ACCDB, or VBA nobody can maintain. Signs repair is enough: one broken form, a failed query after an Office update, or a missing ODBC link. AccessDeveloper advisors review your file structure and give a straight recommendation — repair, refactor, or replace — before you spend money on the wrong path.