ARCHIVING FILES

  • Thread starter Thread starter Pat
  • Start date Start date
P

Pat

I have yearly HR files from 2001 which I need to save but would like to
reduce the number of visible files upon opening. Is there a way to move them
to a folder but keep them active like you can in word and/or excel?
 
What do you mean by a 'file'?
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".
 
I have yearly HR files from 2001 which I need to save but would like to
reduce the number of visible files upon opening. Is there a way to move them
to a folder but keep them active like you can in word and/or excel?

I see that you mean tables and queries, but...

in a properly designed database you will not HAVE annual tables or annual
queries. There should be just one table of (say) Employees, and one table of
Payroll, etc.; and you should have parameter queries which use forms
references to determine the date range.

What are the objects you're attempting to archive? Is this a split database
with the tables in a shared backend and the forms, queries etc. in a frontend
(if not it should be)? More details please!
 
Sorry, you are talking way above my knowledge!
I took over this database and simply followed what was already set.
It appears that there is one table which stores ALL personal info., there
are approx. 40 fields in the table, then queries, forms and reports are made
from the info. in this table as needed. The table is then copied from one
year to the next and inactive files are deleted from the newest table so that
looking back there are records for any employee over the years.
I know that this is not the best solution for setting up the office files
but it is where I started and appears to work for our needs. If there is a
simple way to convert this going forward I would look at it, our office is
filled with computer novices so the simpler the better.
 
Back
Top