I'm still a bit fuzzy on the structure of your data, but it sounds like you
created one table per store, per file/info type. Regardless of where the
data originates, there's no reason why you couldn't create a well-normalized
data structure in Access, and "parse" the incoming data into the correct
tables.
If you are saying you have identically-structured records coming from
multiple stores, all like-structured data belongs in one table, with the
storeID to show which one it belongs to.
It sounds like you are saying the data you receive concerning food costs is
NOT structured the same way the the one for labor hours is structured. But
if all this information is related to a specific store, why not put all the
related information together?
A comment on your example... any time I see repeating fields (in your
example, "DEPOSIT1", "DEPOSIT2", "DEPOSIT3", ...) I see ... a spreadsheet!,
not a relational database.
Forget the initial way the data is organized for a moment and consider how
the data is related. Build your Access table structure accordingly. Then
figure out how to transform the incoming data into the relational structure
....
Good luck!
Jeff Boyce
Microsoft Office/Access MVP