W.W.D.D.
What would Dilbert do?

To summarize: you have a working Excel application that is doing the
job, but the suits want it entered in Access. Do you know why? Do
they expect the work flow to expand so dramatically that it will
require a database?

You may want to explain that Excel is much more intuitive for most
people, and that the amount of time required to develop an Access
database to do a job that's already being done is not worth the payoff.

The pure Dilbert solution is to continue doing it in Excel and create a
dummy database that provides the "cool"? factor the suits are looking
for. Go on vacation and have someone else try to generate your report
from the dummy database; they'll fail because it never worked in the
first place. Your choice at that point is to either casually provide
the report or "work all night to recover the data" and provide the
report, again from Excel.