Thanks for the fuller description. Bins are alphabetic, that makes more sense. I had the impression you were describing part storage by 'alpha-partname'.
But a word of
caution! for consideration.
Having 2 separate Inventory systems/applications (java-based, and an Access based smaller system) to be used by several pickers is prone to issues. If the 2 systems/databases don't get synchronize "auto-majicaly", then you're never quite sure of the contents(parts contained) in any Bin- again a source of issues. This could be considered a
silo approach.
A single table "database" for an Inventory is a non-starter --you really should start with a normalized structure and learn/understand/become familiar with database concepts.
What exactly is the current status of this proposed Access database? Do you have it populated as a single table now?
Are there plans to move this new "customer" into the java-based application?
Is there a IT or database group involved - or - is this something you're just thinking about?
In your own view, what would be the ideal situation given the customers you currently have and the expectations for the business for the future?
NOTE:
Here is a 26 minute video on a building a Stock Control system in Access. You will get some ideas of Access' capabilities and an appreciation of database design.