The specification could call for a multi-user application. Thanks to race conditions in Access, it will look like it is working, and then as the number of users scale up, it will start randomly locking up.
If the application is multi-user, then tell the person who is paying you that the chosen toolset is inappropriate to the task. Because it really is - Access has race conditions which will be a source of unfixable problems in the application. Nor does Microsoft have any incentive to fix this - the aforementioned flakiness is how they push people to pay for the upgrade from Access to SQL Server.
Cheers,
Ben