Updating Tables/Queries from last year gets no results!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Once a year I update several .mdb files for an elementary school PTA. This
year I simply pulled up all of last years' tables, copied them to new names
and updated the records. I thought that I could do the same with the queries
(that worked last year and still work) but now I get no selected records.
Checked and rechecked field names, relationships etc. but no luck. It seems
suspicious that I get NOTHING from any of the dozen or so queries. I cant
even seem to create new ones that return any results at all. What's up?

I would appreciate any advice. I am truely an -

AccessNovice
 
Once a year I update several .mdb files for an elementary school PTA. This
year I simply pulled up all of last years' tables, copied them to new names
and updated the records. I thought that I could do the same with the queries
(that worked last year and still work) but now I get no selected records.
Checked and rechecked field names, relationships etc. but no luck. It seems
suspicious that I get NOTHING from any of the dozen or so queries. I cant
even seem to create new ones that return any results at all. What's up?

I would appreciate any advice. I am truely an -

AccessNovice
Click to expand...

Well... DON'T DO IT THAT WAY!

Renaming tables is *NOT* necessary, and as you have found it is *NOT*
a good way to go. Your tables' names are not data; if you have tables
named Members2004 and Members2005, *you are on the wrong track*. Data,
such as dates or years, is just data, and should be stored IN tables;
if you want to find out information for 2004, or 2005, use a Query
searching on that data.

You certainly would NOT need to or want to rename the queries, even if
you do (unwisely, IMO) rename the tables; what you would need to do
instead is to edit the Queries to change all the references to your
old table names to the new tablenames. This is a tedious process and
prone to error.

Without knowing anything about the structure of your old or new
database, how your queries are set up, or what changes you made I
can't tell you how to solve your current problem; all I can suggest is
that you look at the actual contents of your tables, and logically
build up the queries one join at a time, and see where the data is
getting lost.

John W. Vinson[MVP]
 
Back
Top