Viewing Query Output

 

File:  Queries.xls   

 

This application copies access query output to excel worksheets. 


Uses

- viewing & manipulating query output from the excel (alternative to viewing it in access)

- exporting output to other applications (spreadsheets, reports, etc)   

- checking linked fields in the access tables 

- inventories & statistical summaries of data in various categories   

- copying database tables (ones that will fit in excel)

 

 

Instructions


See general instructions on installation and the user interface .

Select a query from the menu .

Click the 'Run Selected Query'  or the 'Run All Queries' button.

Each worksheet contains a copy of the output from the corresponding query or table in the access database.

New query names can be added to the bottom of the list (col A), if defined in the database.

The queries can be modified in access to restrict coverage based upon site, date, category, etc. 

Modifying the sheets will not change records in the access database.

If error messages occur,  save & close excel, then restart (see installation )

The 'pivot_tables.xls' application provides an alternative method for viewing and summaring query output

Additional queries can be added to the bottom of the list below the menu screen.  When selected, the output will be retrieved and placed in a new worksheet, if it will fit.


 
Check Queries
 
'Check..' queries verify table linkages.  Each is designed to retrieve no records if the tables are properly linked and the required linking variables are defined.  These should be examined after updating the database. The table below the menu screen counts the number of records in output from each of the check queries.  Edit access tables & repeat until no records are listed in the "Check_" sheets.
 
The check queries provide limited verification of the database integrity, they are not intended to be comprehensive and other errors may develop when updating the databases and go undetected by the check queries. 
 
Similarly, the queries may retrieve records that are not fatal flaws. For example, the check_sites query may identify site codes in the site table that are not present in the samples table. This may occur, for example, if the site code refers to a record in the field_data table but not the sample table.