No. You might design spreadsheets like that, but it is the wrong design for
a database.

If you have 46 tables, and many of them have with similar fields, that is
not a normalized design.

If you have repeating fields in a table (such as columns for Jan, Feb, ...,
or Employee1, Employee2, ...), i.e. columns where a user might want to
select which one, then that's not a normalized design either.

Consequently, the database is not set up to query like that.

Grasping the concept of what fields to store in what tables to get a
normalized design is not something you can achieve in 5 minutes. If you want
to follow it through, here's a starting point:
   http://www.accessmvp.com/JConrad/accessjunkie/resources.html#DatabaseDesign101

Well you would need a query to tell you which fields have data.

What you want could be done with VBA.

The basic query to find which fields have data in a specific table would be

SELECT Count(FieldA) as CountFieldA
, Count(FieldB) as CountFieldB
, Count(FieldC) as CountFieldC
FROM SomeTable

Any CountField? that was zero would need to be excluded when you built
the list of fields.

How good are your VBA skills?

'====================================================
 John Spencer
 Access MVP 2002-2005, 2007-2008
 Center for Health Program Development and Management
 University of Maryland Baltimore County
'====================================================